deps

To audit dependencies for security vulnerabilities, you can run a scan using govulncheck for Go projects and npm audit for JavaScript projects. This identifies known security issues and exports the findings into an Obsidian report.

Checking outdated dependencies and license liabilities involves scanning your project libraries to flag outdated versions and verify their license compliance. The tool categorizes these findings and generates an Obsidian-ready report in the Dependencies folder.

Yes, you can run a security-only audit without checking for outdated libraries. The tool supports full audits, security-only checks, updates-only checks, or licenses-only checks, allowing you to isolate vulnerability detection using govulncheck and npm audit.

Dependency auditing works with both Go and JavaScript codebases. It automatically applies the appropriate scanning tools, such as govulncheck for Go and npm audit for JavaScript, to detect vulnerabilities and license issues across both environments.

The best way to generate an audit trail for dependency remediation is to run a full audit that exports structured results to an Obsidian vault. This creates a categorized report of vulnerabilities, updates, and licenses for planning.

An automated dependency audit handles license compliance verification by scanning your project's libraries and highlighting potential license issues. It structures these findings alongside security and update checks within an Obsidian-ready report.