|author||Julie Qiu <email@example.com>||Thu Nov 04 22:08:22 2021 -0400|
|committer||Julie Qiu <firstname.lastname@example.org>||Mon Nov 08 16:33:15 2021 +0000|
internal/worker: add standard library keywords Add keywords in the reference data that would identify a CVE as a Go vulnerability data are added. Change-Id: I5e237486dd7e2a56acb41706b523d3f036cbe53e Reviewed-on: https://go-review.googlesource.com/c/vuln/+/362240 Trust: Julie Qiu <email@example.com> Run-TryBot: Julie Qiu <firstname.lastname@example.org> TryBot-Result: Go Bot <email@example.com> Reviewed-by: Jonathan Amsterdam <firstname.lastname@example.org>
This repository is a prototype of the Go Vulnerability Database. Read the Draft Design.
Neither the code, nor the data, nor the existence of this repository is to be considered stable until an approved proposal.
Important: vulnerability entries in this repository are represented in an internal, unstable format that can and will change without notice.
Database clients must not rely on the contents of this repository. Instead, they can access the tree of JSON entries rooted at
index.json file maps module paths to last modified timestamps (link).
For each module, a
NAME.json file contains a list of vulnerability entries (example).
Note that this path and format are provisional and likely to change until an approved proposal.
Some of these packages can probably be coalesced, but for now are easier to work on in a more segmented fashion.
osvprovides a package for generating OSV-style JSON vulnerability entries from a
clientcontains a client for accessing HTTP/fs based vulnerability databases, as well as a minimal caching implementation
cmd/dbdiffprovides a tool for comparing two different versions of the vulnerability database
cmd/gendbprovides a tool for converting YAML reports into JSON database
cmd/linterprovides a tool for linting individual reports
cmd/report2cveprovides a tool for converting YAML reports into JSON CVEs
Unless otherwise noted, the Go source files are distributed under the BSD-style license found in the LICENSE file.