supply-chain-security

Assess software supply-chain security across SBOM, SCA, CI/CD pipelines, and container images.

21|8|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/chengzongcai/reverse-skill-backup --skill supply-chain-security-chengzongcai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: supply-chain-security
Source: https://github.com/chengzongcai/reverse-skill-backup/tree/main/skills/supply-chain-security
Command: npx skills add https://github.com/chengzongcai/reverse-skill-backup --skill supply-chain-security-chengzongcai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Modern applications depend on hundreds of third-party components, and teams struggle to know which dependencies are vulnerable, whether CI/CD pipelines are tamper-proof, and whether container images can be trusted. This Skill provides a repeatable six-layer methodology for auditing the entire software supply chain instead of guessing at ad-hoc scans. ## Core Features & Use Cases - SBOM Generation and Audit: Generate CycloneDX or SPDX bills of materials with cdxgen, Syft, or sbom-tool, then audit for unknown, abandoned, or license-conflicting dependencies. - SCA and Vulnerability Reachability: Scan with OSV-Scanner, Trivy, Dependency-Track, or Snyk, then verify which CVEs are actually reachable using data-flow analysis and PoC validation instead of trusting raw alert counts. - CI/CD and Container Hardening: Audit GitHub Actions/GitLab CI configurations for injection and permission risks, scan images with Trivy, and sign artifacts with Cosign. - Use Case: Before a compliance review, generate an SBOM for your application, scan it for critical CVEs, verify reachability of the top findings, and produce a prioritized remediation list with evidence. ## Quick Start Use the supply-chain-security skill to generate an SBOM for this repository and audit its dependencies for reachable critical vulnerabilities.

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 my project?▼

Generate a CycloneDX SBOM from source with cdxgen, or use Syft to produce SPDX output from a container image or directory. Microsoft's sbom-tool is another option for build-pipeline integration.

What is the difference between OSV-Scanner, Trivy, and Snyk?▼

OSV-Scanner is free and fast against the OSV.dev database, Trivy covers containers, filesystems, and IaC, while Snyk is commercial and adds vulnerability reachability analysis. Dependency-Track provides continuous monitoring by ingesting SBOMs.

Why do SCA tools report so many false positives?▼

Most SCA alerts flag vulnerable package versions without checking whether your code actually calls the vulnerable function. Only about 15 percent of alerts are typically reachable, so verify with data-flow analysis or PoC testing before prioritizing fixes.

How do I secure a GitHub Actions pipeline against supply-chain attacks?▼

Pin third-party actions to commit SHAs instead of tags, avoid pull_request_target triggers with secrets, set minimal token permissions, and scan for hardcoded credentials with Gitleaks. Sign build artifacts with Cosign for integrity verification.

Does Trivy scan container images for vulnerabilities?▼

Yes, Trivy scans container images across OS packages, application dependencies, and configuration issues. Use severity filters like HIGH and CRITICAL to focus on the most urgent findings.