data. Package names, versions and ecosystems are sent to the OSV.dev API unless you use offline mode.
Who it is forA developer who wants a fast check of a repo's lockfiles before a release.
The problemDependencies pick up known vulnerabilities after you ship.
The outcomeA list of vulnerabilities found in the supported package files.
What you need first
- A prebuilt binary from the releases page, or Go to run go install
- A project directory with lockfiles or manifests, or a container image
- Network access to OSV.dev, unless you use offline mode
Steps
- Download a prebuilt binary from the releases page, or build from source with
go install github.com/google/osv-scanner/v2/cmd/osv-scanner@latest - Run
osv-scanner scan source -r /path/to/your/dir - Read the vulnerabilities reported for files like package.json or go.mod
- Upgrade the affected dependencies and rescan
Prompt for your agent
Using google/osv-scanner, install it with `go install github.com/google/osv-scanner/v2/cmd/osv-scanner@latest`, run `osv-scanner scan source -r /path/to/your/dir` on <my repo>, and summarise the findings by severity with the fix for each.
Caveat. These are the V2 instructions; V1 has its own README.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for google/osv-scanner and "Scan a project for vulnerable dependencies"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer