Add CPE to cargo dependency metadata #187
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
In #181 we added the
jam update-dependencies
command to keep our buildpack dependencies up to date with our new dependency server. This PR results in abuildpack.toml
with the same fields onmetadata.dependency
that we have always had.This PR adds in the support for the new
CPE
field (common platform enumeration) field on each dependency, since this is important for vulnerability lookup.The resulting
buildpack.toml
dependencies will look like:Use Cases
Our dependency server provides CPE notation for each dependency so that we can look up specific vulnerabilities in a NIST database, for example. This is helpful information to surface, so that we can include it in a bill of materials down the line.
Checklist