How github/advisory-database works
This repository is a community-maintained database of security advisories, stored as individual OSV-formatted records. The principal workflow is that advisory information arrives from external databases or community submissions, is reviewed by GitHub’s security advisory curation team, and is merged into the records for downstream readers and systems. The tree shows the reviewed-advisory collection, but no application source; relationships and capabilities beyond that collection are therefore represented only where the README documents them.
Main entry points: github-reviewed Reviewed advisories
Components 13
Advisory intake
- Advisory sources
- Improvement form
- Pull request
Curation workflow
- Security curators
- Supported ecosystems
advisories/github-reviewed
Advisory database
- Reviewed advisories
advisories/github-reviewed - OSV records
advisories/github-reviewed - GHSA identifiers
advisories/github-reviewed - Database-specific values
advisories/github-reviewed
Records and use
- Advisory readers
- Consuming systems
Other components
- Community contributors
- Original publisher
Connections 13
- Advisory sources → Reviewed advisories: provide advisories
- Community contributors → Improvement form: suggest changes
- Improvement form → Pull request: opens
- Community contributors → Pull request: submit directly
- Pull request → Security curators: review
- Security curators → Reviewed advisories: merge or close
- Security curators → Original publisher: mention optionally
- Reviewed advisories → OSV records: formatted as
- Reviewed advisories → GHSA identifiers: assigned identifiers
- Reviewed advisories → Database-specific values: includes metadata
- Reviewed advisories → Supported ecosystems: constrained by
- Advisory readers → Reviewed advisories: read advisories
- Consuming systems → Reviewed advisories: consume records