supply-chain-security

Generate SBOMs, scan dependencies for CVEs, and enforce license compliance.

150|48|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/irahardianto/awesome-agv --skill supply-chain-security-irahardianto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supply-chain-security
Source: https://github.com/irahardianto/awesome-agv/tree/main/.agents/skills/supply-chain-security
Command: npx skills add https://github.com/irahardianto/awesome-agv --skill supply-chain-security-irahardianto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the risk of supply-chain compromises by helping you identify vulnerable or non-compliant dependencies before they reach production.

Core Features & Use Cases

  • CVE scanning across common ecosystems: Use language-specific security tooling (e.g., govulncheck, cargo audit, pip-audit) to find known vulnerabilities in dependency graphs.
  • SBOM generation for traceability: Produce CycloneDX-compatible SBOMs so you can track direct and transitive components across releases.
  • License compliance review and enforcement: Classify licenses by risk (permissive to copyleft) and help automate allowlist/denylist checks in CI.
  • Dependency pinning and artifact verification guidance: Ensure lockfiles and integrity hashes are used to prevent tampering and reduce surprise upgrades.
  • Use Case: Prepare a release candidate by verifying that all dependencies are pinned, scanning for critical CVEs, generating an SBOM for downstream auditing, and failing CI if disallowed licenses are detected.

Quick Start

Use the supply-chain-security skill to scan your project dependencies, generate an SBOM, and confirm license compliance for your next release.

Frequently Asked Questions about supply-chain-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an SBOM for dependency traceability in my CI pipeline?

To generate an SBOM for dependency traceability, you produce CycloneDX-compatible documents that track direct and transitive components across releases. This enables structured reporting for downstream auditing and artifact provenance verification.

Can I scan dependencies for known CVEs across different language ecosystems?

Yes, you can scan dependencies for known CVEs across common ecosystems using language-specific security tooling like govulncheck, cargo audit, or pip-audit. This identifies vulnerable dependencies before they reach production.

How do I enforce license compliance and block disallowed licenses automatically?

You enforce license compliance by classifying dependency licenses by risk from permissive to copyleft, then automating allowlist and denylist checks. This fails CI pipelines if disallowed licenses are detected during releases.

What is the best way to secure software supply chains using dependency pinning?

Securing software supply chains using dependency pinning involves enforcing lockfiles and integrity hashes to prevent tampering. This reduces surprise upgrades and ensures artifact verification before deploying release candidates.

Does this supply chain security approach work for incident response workflows?

Yes, this supply chain security approach applies to incident response workflows triggered by vulnerability disclosures. It scans dependency graphs for critical CVEs and generates structured reports to audit affected artifacts.