OSV (Open Source Vulnerabilities)
OSV is an open data format for vulnerability advisories and a free database, OSV.dev, that collects advisories for open source packages from GitHub, PyPI, RustSec, Go, Linux distributions and others in that format.
Last updated: November 13, 2026
OSV stands for Open Source Vulnerabilities. The name covers two things: the OSV schema, an open JSON format for describing a vulnerability in terms of the packages and versions it affects, and OSV.dev, a free database and API that collects advisories from many sources in that format. Where a CVE record names a vulnerability, an OSV record answers the question a developer actually asks: is the version of this package that I use affected?
Who runs OSV
Google launched OSV in February 2021, starting with vulnerabilities found by its OSS-Fuzz fuzzing service. The schema is now maintained in the Open Source Security Foundation's osv-schema repository and is called the OpenSSF vulnerability format; the database and its infrastructure are open source in google/osv.dev.
OSV.dev does not write most of its advisories. It aggregates databases that publish in the OSV format, such as the GitHub Advisory Database, the PyPI and Python Software Foundation databases, the Go Vulnerability Database, RustSec, OpenSSF Malicious Packages, Ubuntu, Red Hat, Chainguard and Android. For Debian, Alpine and NVD CVEs about open source software, the OSV.dev team converts the source data itself (data sources).
OSV ID prefixes
Every OSV record has an ID of the form <DB>-<ENTRYID>, where the prefix names the database that published it. Some of the prefixes defined in the schema:
| Prefix | Database | Example ID |
|---|---|---|
| GHSA | GitHub Advisory Database | GHSA-jfh8-c2jp-5v3q |
| PYSEC | PyPI Vulnerability Database | PYSEC-2021-123 |
| RUSTSEC | RustSec Advisory Database (crates.io) | RUSTSEC-2021-0001 |
| GO | Go Vulnerability Database | GO-2022-0236 |
| MAL | OpenSSF Malicious Packages | MAL-2025-1234 |
| CVE | NVD records converted by OSV.dev | CVE-2021-44228 |
| OSV | Allocated by OSV.dev, currently only for OSS-Fuzz | OSV-2020-111 |
The same vulnerability often has several records, one per source. The aliases field links them: GHSA-jfh8-c2jp-5v3q, the GitHub advisory for Log4Shell, lists CVE-2021-44228 as its alias, so tools can count it once. MAL- records are different in kind: they describe malicious packages, which have no fixed version.
What an OSV record looks like
The core of a record is the affected list: for each package, its ecosystem, its name and the version ranges that are vulnerable, with events that say where a range was introduced and where it was fixed. Here is GHSA-jfh8-c2jp-5v3q, shortened to one of its ranges:
{
"schema_version": "1.9.0",
"id": "GHSA-jfh8-c2jp-5v3q",
"aliases": ["CVE-2021-44228"],
"summary": "Remote code injection in Log4j",
"published": "2021-12-10T00:40:56Z",
"affected": [{
"package": {
"ecosystem": "Maven",
"name": "org.apache.logging.log4j:log4j-core",
"purl": "pkg:maven/org.apache.logging.log4j/log4j-core"
},
"ranges": [{
"type": "ECOSYSTEM",
"events": [{ "introduced": "2.13.0" }, { "fixed": "2.15.0" }]
}]
}]
}
Ranges can be SEMVER, ECOSYSTEM (the ecosystem's own version ordering, as for PyPI or Debian) or GIT, which gives commit hashes. Git ranges let OSV.dev match a vulnerability to a commit in C and C++ code that has no package manager at all.
OSV vs NVD and CVE
| Question | CVE record | NVD | OSV |
|---|---|---|---|
| What it is | ID and short record | NIST database that enriches CVEs | Format plus aggregated database |
| Identifies software by | Vendor and product text | CPE names | Ecosystem and package name, or a Git repo |
| Affected versions | As the CNA wrote them | CPE version ranges | Machine-readable ranges in each ecosystem's own version scheme |
| Covers advisories without a CVE | No | No | Yes, such as many RUSTSEC, PYSEC and MAL records |
| Best for | Naming one vulnerability | Commercial and closed products | Open source dependencies |
Because OSV is keyed by ecosystem and package, it lines up directly with a lockfile or with the package URL of a component in an SBOM, without the guesswork of mapping a package to a CPE. It is weaker for closed source products and appliances, which have no package ecosystem and are described in the NVD.
The OSV API and osv-scanner
The API at https://api.osv.dev is free, and its documentation states no usage limits. A query by package and version:
curl -d '{"package": {"name": "nokogiri", "ecosystem": "RubyGems"}, "version": "1.18.2"}' \
"https://api.osv.dev/v1/query"
/v1/querybatch checks many packages in one request, and /v1/vulns/{id} returns one record. The whole database can also be downloaded per ecosystem.
OSV-Scanner, announced in December 2022, is Google's command-line front end to the database. It scans lockfiles, SBOMs, directories and container images and reports the OSV records that match.
How CRACI relates
CRACI shows each package's advisories, with their CVE, GHSA and other IDs and their severity, for the components recorded in each build. For what an SBOM must contain before any database can match it, see build-time SBOMs.