Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://google.github.io/osv.dev/
Open source vulnerability DB and triage service.
https://google.github.io/osv.dev/
security security-tools vulnerability vulnerability-databases vulnerability-management vulnerability-scanners
Last synced: about 2 months ago
JSON representation
Open source vulnerability DB and triage service.
- Host: GitHub
- URL: https://google.github.io/osv.dev/
- Owner: google
- License: apache-2.0
- Created: 2021-01-08T02:14:10.000Z (almost 4 years ago)
- Default Branch: master
- Last Pushed: 2024-05-10T04:59:49.000Z (6 months ago)
- Last Synced: 2024-05-10T05:35:14.382Z (6 months ago)
- Topics: security, security-tools, vulnerability, vulnerability-databases, vulnerability-management, vulnerability-scanners
- Language: Python
- Homepage: https://osv.dev
- Size: 19.9 MB
- Stars: 1,412
- Watchers: 41
- Forks: 172
- Open Issues: 184
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/google/osv.dev/badge)](https://scorecard.dev/viewer/?uri=github.com/google/osv.dev)
## Documentation
Comprehensive documentation is available [here](https://google.github.io/osv.dev).
API documentation is available [here](https://google.github.io/osv.dev/api/).## Viewing the web UI
An instance of OSV's web UI is deployed at .
## Using the scanner
We provide a Go based tool that will scan your dependencies, and check them against the OSV database for known vulnerabilities via the OSV API.
Currently it is able to scan various lockfiles, debian docker containers, SPDX and CycloneDB SBOMs, and git repositories.
The scanner is located in its [own repository](https://github.com/google/osv-scanner).
## This repository
This repository contains all the code for running https://osv.dev on GCP. This
consists of:| directory | what |
|-----------------|------|
| `deployment/` | Terraform, Cloud Deploy & App Engine config files
A few Cloud Build config yamls
Old (no longer used?) `api-staging` and `api-test` Cloud Run configs |
| `docker/` | CI docker files (`ci`, `deployment`, `terraform`)
Workers for bisection and impact analysis (`worker`, `importer`, `exporter`, `alias`, `worker-base`)
The determine version `indexer`
`cron/` jobs for database backups and processing oss-fuzz records |
| `docs/` | Jekyll files for https://google.github.io/osv.dev/
`build_swagger.py` and `tools.go` |
| `gcp/api` | OSV API server files (including files for the local ESP server)
protobuf files in `/v1`|
| `gcp/appengine` | The backend of the osv.dev web interface, with the frontend in `frontend3`
Blog posts (in `blog`)
App Engine Cron Handlers (to be removed)
The datastore indexes file (`index.yaml`) |
| `gcp/functions` | The Cloud Function for publishing PyPI vulnerabilities (maintained, but not developed) |
| `osv/` | The core OSV Python library, used in basically all Python services
OSV ecosystem package versioning helpers in `ecosystems/`
Datastore model definitions in `models.py` |
| `tools/` | Misc scripts/tools, mostly intended for development (datastore stuff, linting)
The `indexer-api-caller` for indexer calling |
| `vulnfeeds/` | Go module for (mostly) the NVD CVE conversion
The Alpine feed converter (`cmd/alpine`)
The Debian feed converter (`tools/debian`, which is written in Python) |You'll need to check out submodules as well for many local building steps to
work:```bash
git submodule update --init --recursive
```## Contributing
Contributions are welcome!
Learn more about [code](CONTRIBUTING.md#contributing-code), [data](CONTRIBUTING.md#contributing-data), and [documentation](CONTRIBUTING.md#contributing-documentation) contributions.
We also have a [mailing list](https://groups.google.com/g/osv-discuss).Do you have a question or a suggestion? Please [open an issue](https://github.com/google/osv.dev/issues).
## Third party tools and integrations
There are also community tools that use OSV. Note that these are community built
tools and as such are not supported or endorsed by the core OSV maintainers. You may wish
to consult the [OpenSSF's Concise Guide for Evaluating Open Source Software](https://best.openssf.org/Concise-Guide-for-Evaluating-Open-Source-Software)
to determine suitability for your use. Some popular third party tools are:- [Cortex XSOAR](https://github.com/demisto/content)
- [dep-scan](https://github.com/AppThreat/dep-scan)
- [Dependency-Track](https://github.com/DependencyTrack/dependency-track)
- [GUAC](https://github.com/guacsec/guac)
- [OSS Review Toolkit](https://github.com/oss-review-toolkit/ort)
- [pip-audit](https://github.com/pypa/pip-audit)
- [Renovate](https://github.com/renovatebot/renovate)
- [Trivy](https://github.com/aquasecurity/trivy)