You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Support more complex human-friendly upstream bug URLs by allowing
templating rather than simple appending of the the bug ID to a URL.
This allows AlmaLinux and Curl human-friendly links to be added to the
frontend UI in addition the what's already there.
Also add an FAQ about data fixes, which can be referenced from the bug
template
Copy file name to clipboardExpand all lines: docs/faq.md
+21-1Lines changed: 21 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ Vulnerability databases can also benefit from easier interchange and vulnerabili
80
80
81
81
Yes!
82
82
83
-
The database in available in a GCS bucket maintained by OSV: [gs://osv-vulnerabilities](https://osv-vulnerabilities.storage.googleapis.com/) (also [publicly browseable via the Google Cloud Console](https://console.cloud.google.com/storage/browser/osv-vulnerabilities) with a login)
83
+
The database in available in a GCS bucket maintained by OSV: [gs://osv-vulnerabilities](https://storage.googleapis.com/osv-vulnerabilities/index.html) (also [publicly browseable via the Google Cloud Console](https://console.cloud.google.com/storage/browser/osv-vulnerabilities) with a login)
84
84
85
85
More information about how to download the database is available [here](data.md#data-dumps).
86
86
@@ -111,3 +111,23 @@ If you work on a project (like a Linux distribution) and would like to contribut
111
111
## Is the API rate limited?
112
112
113
113
No. Currently there is not a limit on the API.
114
+
115
+
## I've found something wrong with the data
116
+
117
+
Data quality is very important to us. Please remember that OSV.dev is an
118
+
aggregator of OSV records from a [variety of
119
+
sources](https://github.com/google/osv.dev/blob/master/source.yaml) and the most
120
+
appropriate place to correct the data is at the source.
121
+
122
+
We prefer to avoid needing to act as a broker between downstream consumers of
123
+
the data and upstream sources, as this adds limited value, and only adds delays.
124
+
125
+
Where available, a human-friendly link to the authoritative record source is
126
+
available as the `Source` field on the individual vulnerability page. You should
127
+
follow the source-specific process for updating the data.
128
+
129
+
For sources that are a Git repository, the `Import Source` field points to the
130
+
authoritative source of the data, and you may be able to create a pull/merge
131
+
request or file an issue against the repository.
132
+
133
+
If you are not able to get satisfaction after dealing directly with the source of the data, please [file an issue](https://github.com/google/osv.dev/issues?q=is%3Aissue+is%3Aopen+label%3A%22data+quality%22) tagged with `data quality`.
0 commit comments