docs: keep SLSA claims tied to release evidence - #32
Merged
Merged
Conversation
Signed-off-by: IanHollow <72767437+IanHollow@users.noreply.github.com>
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
Remove the generic
SLSA statusREADME badge. Its image is fixed and does not report a verified level, a release subject, or a fresh result. Keep the OpenSSF Scorecard badge, which links to a published, updated score.The SLSA assessment remains at https://github.com/nix-forge/.github/blob/main/docs/slsa.md. A future level badge should identify the exact artifact, SLSA track and specification version, and link to a release verification record. The SLSA v1.2 verification summary describes artifact-specific verified levels: https://slsa.dev/spec/v1.2/verification_summary.
Validation
git diff --check.gitleaks git --pre-commit --staged --redact --no-banner; no leaks found.Documentation-only change; no build or runtime behavior changed.