Add Proof of Commitment to Supply Chain Security#153
Open
piiiico wants to merge 1 commit into
Open
Conversation
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.
Adds Proof of Commitment to the Supply Chain Security section.
What it does: Scores npm, PyPI, Cargo and Go packages on behavioral commitment signals — publisher depth, release consistency, maintenance patterns — that predict supply chain risk before attacks happen. Both axios and chalk scored CRITICAL before their 2026 compromises.
How it ships:
npx proof-of-commitment)poc hook)Different from existing entries: operates on behavioral signals rather than vulnerability databases (Snyk/Dependabot) or build-time integrity (Sigstore/Preflight).