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
By enrich, we mean add additional information. You put in an SBOM, and you get a richer SBOM back. In many cases SBOMs have a minimum of information, often just the name and version of a given package. By enriching that with additional information we can make better decisions about the packages we're using.
15
16
@@ -191,7 +192,7 @@ Snyk will add a new [vulnerability](https://cyclonedx.org/docs/1.4/json/#vulnera
191
192
}
192
193
```
193
194
194
-
For SPDX, vulnerability informatio is added as additional `externalRefs`:
195
+
For SPDX, vulnerability information is added as additional `externalRefs`:
195
196
196
197
```json
197
198
{
@@ -246,6 +247,74 @@ This will currently add an external reference to the [Scorecard API](https://api
246
247
247
248
We're currently looking at the best way of encoding some of the scorecard data in the SBOM itself as well.
248
249
250
+
## Enriching with deps.dev
251
+
252
+
The [deps.dev](https://deps.dev) service provides repository insights and security data for open source packages. `parlay` can enrich SBOMs with repository metadata from deps.dev.
@@ -348,3 +417,7 @@ The various services used to enrich the SBOM data have data for a subset of purl
348
417
*`pypi`
349
418
350
419
Note that Scorecard data is available only for a subset of projects from supported Git repositories. See the [Scorecard project](https://github.com/ossf/scorecard) for more information.
420
+
421
+
### deps.dev
422
+
423
+
deps.dev enrichment works with any component that has VCS external references pointing to supported Git repositories (GitHub, GitLab, etc.).
0 commit comments