OSV-Scanner
v2.7.0 open-sourceThe section your link pointed to isn't on OSV-Scanner's page any more, so we've brought you to the top.
Use OSV-Scanner to find existing vulnerabilities affecting your project’s dependencies.
osv-scanner scan source --x-plugins=zig/buildzigzon -r /path/to/your/zig/project
osv-scanner scan source --experimental-plugins -r /path/to/your/dir
ScanGoModVersion: true
osv-scanner scan source --experimental-plugins -r /path/to/your/dir
scanner, err := osvscanner.New(osvscanner.VulnerabilityScannerArgs{UserAgent: "my-custom-agent"})
osv-scanner --experimental-flag-deprecated-packages .
osv-scanner --experimental-plugins=./my-custom-plugin --experimental-no-default-plugins ./path/to/project
osv-scanner --experimental-plugins=plugin1,plugin2 <path>
osv-scanner scan image nginx:latest
osv-scanner scan . --serve --port 9090
osv-scanner update
osv-scanner fix --experimental-offline-vulnerabilities --experimental-no-resolve ./...
osv-scanner --lock=go.mod --upgrade-config=upgrades.yaml
# examples:
# - package: "github.com/gorilla/mux"
# allowed_versions:
# - ">=1.0.0 <2.0.0"
# - package: "golang.org/x/text"
# allow_major: true
osv-scanner --experimental-offline --experimental-download-offline-databases .
osv-scanner gradle/verification-metadata.xml .
osv-scanner fix
osv-scanner --lockfile nuget.lock --ignore-vulns CVE-2023-1234
osv-scanner --license .
osv-scanner --call-analysis=go ./...
osv-scanner --sarif-format=vuln -f package.json
import osvscanner
ecosystems = osvscanner.GetAllEcosystems()
for eco in ecosystems:
print(eco)
osv-scanner --experimental-call-analysis ./...
osv-scanner -r requirements.txt
osv-scanner --format markdown-table package-lock.json
osv-scanner version
Summary
OSV-Scanner is an open-source vulnerability scanner, free to use, that checks a project's dependencies against the OSV database to find known issues affecting them. It runs as a command-line tool in a terminal or CI/CD pipeline, or can be imported as a Go library for teams building their own scanning logic, which makes it suited to application developers and platform teams responsible for dependency hygiene rather than SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts. It covers over a dozen language ecosystems, package managers, OS packages, and container images, and offers guided remediation that recommends version upgrades based on severity and fix strategy. Its documentation frames the OSV database itself as an advantage over closed-source advisory scanners, citing more precise, actionable results. First committed in 2022, it has 127 contributors and a release roughly every week, with the last one 14 days ago.
Use OSV-Scanner to find existing vulnerabilities affecting your project’s dependencies.
How OSV-Scanner helps
Which of my dependencies pull in a package with a known vulnerability?
checks the project's resolved dependency list, across languages, package managers, and lockfiles, against the OSV database and lists each affected package with the advisory that flags it
Is a vulnerability actually reachable given the versions I'm running?
maps the affected-version ranges in each advisory against the exact versions resolved in the project, so a package that merely appears in a manifest but isn't in a vulnerable range is not flagged
What version should I upgrade to so a flagged package stops being vulnerable?
recommends a specific upgrade based on severity, dependency depth, and fix strategy, rather than just naming the vulnerability
Do my container images carry known-vulnerable packages in their base layers?
scans the image's OS packages and bundled libraries and reports which ones match entries in the database
Are my open-source licenses within the policy I've set?
summarizes the licenses found across dependencies and flags any that fall outside an allowed list
Can I check my dependencies for vulnerabilities without sending data off the machine?
runs the same matching logic against a locally stored copy of the database instead of querying it over the network
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for OSV-Scanner, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail OSV-Scanner puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Coverage
Missing something? Tell us
What OSV-Scanner connects to, runs on and detects, read from its release notes and docs. So far: 2 new supported platforms, 1 new integration, 1 updated supported platform.
4 changes, tracked since Oct 12, 2026.
-
Oct 122026
new Zig build.zig.zon extractor
With zig/buildzigzon
Added `zig/buildzigzon` (`build.zig.zon`, google/osv-scalibr#1841), available via `--x-plugins` (`--experimental-plugins`).
-
Oct 122026
new Bitnami container SPDX SBOM scanning
With sbom/spdx
Support scanning Bitnami container SPDX SBOMs (`sbom/spdx`) (google/osv-scalibr#2156).
-
Oct 122026
new MinimOS ecosystem mapping for APK extractor
With os/apk
Add MinimOS ecosystem mapping to the APK extractor (`os/apk`) (google/osv-scalibr#2406).
-
Oct 122026
updated Dart package_config.json extractor enabled by default
With dart/packageconfig
Enable Dart `package_config.json` (`dart/packageconfig`) extractor by default for lockfile scans (google/osv-scalibr#2295).
Operating systems 2
Languages & runtimes 2
Other 2
Other 1
Nothing first seen in this window. That doesn't mean OSV-Scanner shipped nothing, only that we found no record of it.
How we count
Read from 1 of 44 release notes and docs updates we hold for OSV-Scanner. "First seen" is the earliest note that names something; "last" is the latest. Our history may start partway through OSV-Scanner's life, so an old integration can show a recent first-seen date.
Each change counts once: "added 40 checks" is one line, so the numbers measure how often coverage moves, not how big the catalogue is or how well it detects.
Releases
44 entries
No entries match these filters.
- October 20261
- September 20261
- August 20263
- June 20261
- May 20261
- March 20261
- February 20261
- January 20261
- December 20251
- November 20251
- October 20252
- August 20252
- July 20251
- June 20251
- April 20251
- March 20251
- October 20242
- September 20241
- August 20242
- July 20241
- June 20241
- May 20242
- April 20241
- March 20241
- January 20242
- December 20231
- November 20231
- October 20231
- September 20231
- July 20231
- June 20231
- May 20231
- March 20231
- February 20231
- January 20231
- December 20221
Project health
Issue, contributor and maintainer activity in google/osv-scanner, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 49 +16 vs prior 12 months
- Maintainers 3 +0 joined · −2 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 93% of issues opened, last 12 months
- Median time to close 48 days first maintainer reply 2.3 days
- Open backlog 98 of 553 issues ever filed
- Issues opened / month 5 · 0 communitymaintainers
- Open backlog 98
- Contributors / month 13
- Commits / month 40
- Stars 11,034
- bugs 4%
- features 3%
- other 93%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →