osv-scan

Scan npm dependencies for vulnerabilities with osv-scanner and triage findings via GitHub issues.

1|Updated Aug 18, 2026
One-click install
npx skills add https://github.com/davidsneighbour/clerkwork --skill osv-scan-davidsneighbour
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: osv-scan
Source: https://github.com/davidsneighbour/clerkwork/tree/main/skills/osv-scan
Command: npx skills add https://github.com/davidsneighbour/clerkwork --skill osv-scan-davidsneighbour

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Vulnerability scans produce findings that are hard to track over time: the same advisory gets re-reported, safe fixes are mixed with risky major upgrades, and prior accept-or-fix decisions get lost. This Skill runs osv-scanner against your repository, auto-applies only safe non-breaking fixes, files deduplicated GitHub issues for the rest, and records every decision in a committed ledger so repeat runs never re-file the same vulnerability. ## Core Features & Use Cases - Automated safe fixes: Applies patch/minor version bumps that resolve a finding, re-scans to confirm, and runs the repository validation gate before keeping the change. - Deduplicated issue filing: Searches existing open and closed GitHub issues before creating one per vulnerability ID, with severity mapped to priority labels. - Persistent triage ledger: Tracks accepted, fixed, workaround, and open statuses in memories/osv-scan-ledger.json with dated rationale notes, so decisions survive across runs. - Use Case: Run an OSV scan on an npm monorepo; two findings are auto-fixed with minor bumps, one major-only fix becomes a labeled GitHub issue, and a previously accepted advisory is skipped because its review date has not passed. ## Quick Start Use the osv-scan skill to scan this repository's dependencies for vulnerabilities, apply safe fixes, and file issues for anything unresolved.

Frequently Asked Questions about osv-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I scan npm dependencies for vulnerabilities with osv-scanner?▼

Run osv-scanner scan with JSON output against the repository, then parse the results for vulnerability IDs, aliases, severity, and fixed versions. This Skill automates that flow and cross-references a ledger so known findings are not reprocessed.

How to auto-fix vulnerability findings without breaking upgrades?▼

Only patch and minor version bumps that clear the advisory are applied automatically, followed by npm install, a confirmation re-scan, and the repository validation gate. Major upgrades are never auto-applied; they are filed as GitHub issues instead.

Does osv-scanner send my dependency data to an external service?▼

Yes, osv-scanner sends package-lock.json dependency metadata to the public https://api.osv.dev/v1/querybatch endpoint. Because of that trust boundary, this Skill only runs when explicitly invoked and must not be wired into git hooks, npm scripts, or CI.

Can I avoid duplicate GitHub issues for the same vulnerability?▼

Yes, the workflow searches all open and closed issues for the vulnerability ID before creating anything, and files at most one issue per ID. A committed ledger records each finding's status so repeat runs skip accepted, fixed, and open entries.

What happens when a vulnerability has no fix available?▼

Findings without a safe fix become labeled GitHub issues with severity, aliases, and advisory links. The user can then accept the risk or apply a workaround such as an overrides pin, and that decision is logged with a review date in the ledger.