Supply chain risk of a repository
security_supply_chain_riskAssess whether a repository is safe to depend on by checking supply-chain risk signals: maintainer bus factor, ownership changes, release anomalies, signing, advisories, and OpenSSF Scorecard.
Instructions
Is this project safe to depend on? Checks the warning signs behind real supply chain attacks (xz-utils, event-stream): bus factor, a newcomer suddenly taking over, dormant-then-burst releases, branch protection, commit and release signing, security policy, private vulnerability reporting, Dependabot or Renovate, published advisories, and the OpenSSF Scorecard result. Part of the security toolkit: also call security_audit_dependencies for known vulnerabilities in its dependencies. Uses about 12 GitHub API requests, plus one call to the public OpenSSF Scorecard API with the repository name.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"owner": "<owner>",
"repo": "<repo>"
},
"name": "security_supply_chain_risk"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| repo | Yes | Repository name, e.g. 'spring-boot' | |
| owner | Yes | Repository owner (user or organization), e.g. 'spring-projects' |