Add proof-of-commitment — supply chain risk scoring#1836
Closed
piiiico wants to merge 2 commits into
Closed
Conversation
Author
|
Superseded by #1837 — corrected YAML format. |
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
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.
What
Adds proof-of-commitment as a supply chain security analysis tool.
Why it fits
Supply chain risk is a growing SAST/SCA concern. This tool scores npm packages, PyPI packages, Rust crates, Go modules, and GitHub repos on behavioral commitment signals — publisher count, transfer history, contributor concentration — that traditional vulnerability scanners (which look for CVEs) don't cover.
Similar tools already in the list: Semgrep Supply Chain, OWASP Dependency Check.
Usage
npx proof-of-commitment # auto-detects package.json / lockfile npx proof-of-commitment zod axios chalkAlso available as a web tool: https://getcommit.dev
Tool metadata