Our take
Activeregular commits and releases- Activity
- 76
- Community
- 91
- Issues
- 64
- Pull requests
- 60
+344 stars in the last 30 days
- Merges more pull requests than 86% of the projects we track
- More contributors than 78% of the projects we track
OSV-Scanner is an actively maintained dependency scanner with a broad contributor base and regular releases, making it a credible choice for teams that want OSV-backed checks in a CLI workflow.
Good fit if
- You want vulnerability scanning across multiple package ecosystems, or for supported container artifacts.
- You prefer OSV’s open advisory data and want an offline scanning option.
- You can use a Go CLI and accept Apache-2.0 licensing.
Look elsewhere if
- You need scanning for an ecosystem, lockfile, or container artifact that OSV-Scanner does not support.
- You need guided remediation for formats beyond its documented npm and Maven support.
- You need a vulnerability scanner that does not send package metadata to external services during online operation.
All health signals
| Last commit | 2026-10-12 (1 day ago) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 13 (latest v2.7.0, 2026-10-12) |
| Contributors | 100+ (top contributor: 23% of commits) |
| Issues closed, last 90 days | 12+ (typically closed in 3 days) |
| Pull requests merged, last 90 days | 79 (typically merged in 1 day) |
| Project age | 3 years |
Checked on 2026-10-14 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
11,544Forks
855Change since Nov 16, 2026: +12 stars·0 forks
Overview
OSV-Scanner is a Go command-line tool that connects a project’s dependency inventory to vulnerability records in the OSV database. It helps developers and security teams identify known vulnerabilities in supported package ecosystems without relying on a closed advisory database.
It can scan source directories and container images, and includes options for offline scanning and guided dependency remediation. Its scope is vulnerability discovery and related dependency information, rather than a general-purpose security testing suite.
Key Features
- Recursively scans source directories for supported package and lock files.
- Checks dependencies against the OSV database, with optional call analysis to help identify whether vulnerable functions are used.
- Scans container images for supported operating-system packages and language artifacts.
- Detects vendored C/C++ code for vulnerability scanning.
- Supports offline scans against a local OSV database after downloading the data.
- Provides experimental guided remediation for selected npm and Maven files.
- Checks dependency licenses using deps.dev data.
Use Cases
- Application developers can scan a repository before a release to find known vulnerabilities in its dependencies.
- Security teams can add dependency vulnerability checks to a Go-based CLI workflow across supported ecosystems.
- Platform teams can inspect container images for vulnerabilities in supported Linux distributions and language artifacts.
- Teams in restricted networks can use a locally downloaded OSV database for offline scans.
- Maintainers of npm or Maven projects can try guided remediation when the supported file formats and experimental status suit their workflow.
What you need
Detected in the repository
- Go 1.27.0 or newer (from go.mod)
- Automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install the latest version from the installation documentation, or build from source:
go install github.com/google/osv-scanner/v2/cmd/osv-scanner@latest
Then scan a directory:
osv-scanner scan source -r /path/to/your/dir
See the README and documentation for supported files and options.
Considerations
- Support depends on the package ecosystem, lockfile, and artifact. Check the supported languages and lockfiles before adopting it for a specific project.
- Online operation can send package names, versions, ecosystems, and file hashes to OSV.dev. Some features also use deps.dev or package registries. Offline mode avoids network requests during scans after the database is available locally.
- Guided remediation is experimental and can invoke package-manager scripts or access external registries. The project warns against running it on untrusted projects.
- The project is actively maintained, with recent commits and releases, broad contributor participation, and median issue and pull-request handling times measured in days. That activity is encouraging, but does not guarantee support for every ecosystem or workflow.
Found this useful?
Share it with someone who would like osv-scanner.