supply-chain-security

Audit software supply chains through SBOM generation, SCA scanning, and CI/CD pipeline security checks.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill supply-chain-security-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supply-chain-security
Source: https://github.com/dbx0/skills/tree/main/skills/supply-chain/initial-access/supply-chain-security
Command: npx skills add https://github.com/dbx0/skills --skill supply-chain-security-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Modern applications depend on hundreds of third-party components, and most teams cannot answer which dependencies they ship, which CVEs are actually exploitable, or whether their CI/CD pipeline can be tampered with. This Skill provides a structured methodology for SBOM generation, dependency vulnerability verification, and pipeline hardening. ## Core Features & Use Cases - SBOM Generation and Auditing: Produce CycloneDX or SPDX inventories with cdxgen, Syft, or sbom-tool, then audit for unknown, deprecated, or license-conflicting components. - SCA and Reachability Verification: Scan with OSV-Scanner, Trivy, Dependency-Track, or Snyk, then verify which CVEs are actually reachable using CodeQL data-flow analysis and PoC validation. - CI/CD Pipeline Security: Audit GitHub Actions and GitLab CI configurations for script injection, over-privileged tokens, unpinned actions, secret leakage, and runner isolation gaps. - Use Case: A compliance team needs an SBOM for a customer audit. Generate one with cdxgen, scan it with OSV-Scanner, upload it to Dependency-Track for continuous monitoring, and verify the top CVEs are reachable before filing remediation tickets. ## Quick Start Generate an SBOM for this repository, scan it for known vulnerabilities, and tell me which critical CVEs are actually reachable in our code.

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?

Use cdxgen to produce a CycloneDX SBOM from source code, Syft to generate SPDX from a container image or directory, or Microsoft's sbom-tool for build outputs. CycloneDX suits security analysis while SPDX fits license compliance workflows.

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

OSV-Scanner is free and fast against the OSV.dev database, Trivy scans filesystems, images, and IaC from multiple sources, and Snyk is commercial with reachability tagging. Only Snyk and CodeQL provide reachability analysis out of the box.

How do I verify if a CVE is actually exploitable in my code?

Confirm the installed version manually, check the affected version range on OSV.dev or NVD, then perform reachability analysis with CodeQL data-flow queries or trace execution paths to the vulnerable function. Verify any public PoC in an isolated container before prioritizing fixes.

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

Pin third-party actions to commit SHAs instead of tags, avoid pull_request_target triggers that expose secrets, set least-privilege token permissions, and never interpolate user input into run steps. Scan for hardcoded secrets with Gitleaks or TruffleHog.

Does SCA scanning alone tell me my real vulnerability risk?

No. Only roughly 15 percent of SCA alerts are actually reachable in practice. Combine scanning with reachability analysis, PoC verification, and CVSS-based prioritization to focus remediation on vulnerabilities that pose genuine risk.