AGENT SKILL

devsecops-supply-chain

Generate SBOM (CycloneDX/SPDX), verify SLSA provenance, audit dependency chains, and detect supply chain attack patterns.

License 许可
MIT
最近更新
2026-11-09
Stars
★ 0
Forks
0

01 前言 Front Matter

name
devsecops-supply-chain
source
https://github.com/BuilderCed/agent-skills
license
MIT
version
1.0.0
category
devsecops
language
en
priority
high
platforms
[ "claude-code", "codex", "gemini-cli", "cursor", "copilot", "windsurf", "cline" ]
description
Generate SBOM (CycloneDX/SPDX), verify SLSA provenance, audit dependency chains, and detect supply chain attack patterns.
imported_at
2026-09-20
source_path
skills/devsecops/devsecops-supply-chain/SKILL.md
dependencies
{ "mcp": [], "apis": [], "data": [], "skills": [] }
last-updated
2026-04-17
model_tested
claude-sonnet-4-6
geo_relevance
[ "global" ]
update_sources
[ { "url": "https://slsa.dev/spec/v1.0/", "last_checked": "2026-04-17", "check_frequency": "quarterly" } ]
source_repository
BuilderCed/agent-skills

03 SKILL.md 正文

DevSecOps Supply Chain Security

When to Use

  • Setting up dependency security for a new project
  • Generating SBOM for compliance or audit
  • Investigating a suspicious dependency
  • Responding to a supply chain incident
  • Configuring CI/CD security gates

SBOM Generation

Formats

Format Standard Best For
CycloneDX OWASP Security-focused, VEX support
SPDX Linux Foundation License compliance, legal

Generation Commands

If a terminal is available, use these commands. Otherwise, describe what fields to include manually.

Node.js/npm:

npx @cyclonedx/cyclonedx-npm --output-file sbom.json

Python/pip:

pip install cyclonedx-bom
cyclonedx-py requirements -i requirements.txt -o sbom.json

Go:

cyclonedx-gomod mod -json -output sbom.json

SLSA Compliance Levels

Level Requirement How
SLSA 1 Documentation of build process Document build steps
SLSA 2 Hosted build platform, signed provenance Use GitHub Actions, sign with Sigstore
SLSA 3 Hardened build platform, non-falsifiable provenance Isolated builders, hermetic builds

Supply Chain Attack Patterns

Pattern Detection Prevention
Typosquatting Compare package name to known packages Pin exact versions
Dependency confusion Check if internal name exists on public registry Scope packages, configure registry priority
Compromised maintainer Monitor for unusual releases, new maintainers Pin versions + hashes, delayed adoption
Malicious post-install Audit install scripts --ignore-scripts flag, review before install
Star-jacking Verify GitHub URL matches npm/PyPI metadata Cross-reference package metadata

Dependency Audit Checklist

  1. Are all dependencies pinned to exact versions?
  2. Are lockfiles committed and reviewed in PRs?
  3. Are dependency hashes verified (pip --require-hashes, npm --package-lock-only)?
  4. Is there a delay before adopting new package versions (7+ days)?
  5. Are transitive dependencies audited (not just direct)?
  6. Are install scripts reviewed for new dependencies?
  7. Is there automated vulnerability scanning in CI?

What This Skill Does NOT Do

  • Does not patch vulnerabilities automatically
  • Does not detect zero-day exploits
  • Does not replace tools like Snyk, Dependabot, or pip-audit (complements them)
  • Does not manage secrets rotation

04 同仓库更多 Skills