content: Rename upstreamProvenance to upstreamAttestations - #1648
Open
mlieberman85 wants to merge 1 commit into
Open
content: Rename upstreamProvenance to upstreamAttestations#1648mlieberman85 wants to merge 1 commit into
mlieberman85 wants to merge 1 commit into
Conversation
Pluralize and rename the upstream-attestation field in the Dependency Ingestion Provenance predicate so it can represent verdicts on any upstream-published attestation (Build Provenance, VSA, upstream-signed VEX, or other predicate types), not just Build Provenance. The prior singular name misleadingly suggested Build Provenance only, and the singular shape could not carry verdicts on multiple upstream predicate types at once. - upstreamProvenance (object) -> upstreamAttestations (array) - Each entry identifies a predicateType and carries its own verification verdict plus availability marker. - At L3, at least one entry MUST be present describing the platform's upstream-attestation stance for the dep. - Kept the #dep-verify-provenance HTML anchor stable so external links are not broken. Signed-off-by: Michael Lieberman <mlieberman85@gmail.com>
✅ Deploy Preview for slsa ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Follow-on to #1627. Renames and pluralizes the upstream-attestation field
in the Dependency Ingestion Provenance predicate so it can carry verdicts
on any upstream-published attestation, not just SLSA Build Provenance.
upstreamProvenance(object) →upstreamAttestations(array of entries)predicateTypeand carries its own verificationverdict plus availability marker.
upstream-attestation stance for the dep.
#dep-verify-provenanceHTML anchor stable so existing externallinks are not broken.
Why
The previous singular
upstreamProvenancefield was misleadingly named — thespec text said it could carry a VSA or any other upstream attestation, but
the name implied Build Provenance only. The singular shape also meant the
platform could only reference one upstream attestation per dep, so an
upstream that publishes both a Build Provenance and a VSA could not be
represented cleanly.
Files changed
spec/dependency-provenance.md— field, section, matrix, examples, andverification-step updates.
spec/dependency-track.md— mode-1 reference, L3 summary and requirement,benefits, and S2C2F mapping row.
spec/threats.md— threat-block cross-reference wording.Test plan
npm run lintclean./tools/lint.shclean