security-supply-chain

Audit CI/CD workflows, dependency intake, and release pipelines for software supply chain integrity.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/akoita/agent-toolkit --skill security-supply-chain-akoita
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-supply-chain
Source: https://github.com/akoita/agent-toolkit/tree/main/plugins/claude/security/skills/security-supply-chain
Command: npx skills add https://github.com/akoita/agent-toolkit --skill security-supply-chain-akoita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve? Modern attacks target the build and release pipeline rather than application code: force-moved action tags, malicious npm install scripts, and unsigned artifacts. This Skill gives a structured, evidence-based method to harden a repository's entire software supply chain, from GitHub Actions workflows to SBOMs, signing, and compliance obligations. ## Core Features & Use Cases - CI/CD Hardening: Runs zizmor and actionlint against workflows, pins actions to commit SHAs with pinact, enforces least-privilege permissions, and blocks dangerous pull_request_target patterns. - Dependency Intake Policy: Applies deterministic-versus-soft-signal disposition rules for vulnerable, malicious, abandoned, or newly published packages, with lockfile discipline and release cooldowns. - Provenance and Compliance: Generates CycloneDX SBOMs with syft, signs artifacts with cosign keyless mode, produces SLSA build provenance, and maps controls to OpenSSF Scorecard, OSPS Baseline, EU CRA, NIST SSDF, and OWASP ASVS. - Use Case: Point it at a repository before a release to get a tiered security profile, SHA-pinned workflows, a validated Action Bill of Materials, and a findings report with file:line evidence for every issue. ## Quick Start Review this repository's supply chain security, starting with the GitHub Actions workflows, and produce a tiered findings report with an SBOM and pinned action references.

Frequently Asked Questions about security-supply-chain

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

FAQPage Schema
How do I pin GitHub Actions to commit SHAs?▼

Use pinact to rewrite uses: refs to commit SHAs while keeping version comments: run pinact run --check to report unpinned actions and pinact run to rewrite them. Dependabot understands SHA pins with trailing version comments, so updates keep working.

How do I audit GitHub Actions workflows for security issues?▼

Run zizmor for security audits like template-injection, artipacked, and excessive-permissions, plus actionlint for schema and expression correctness. Use --format sarif or --no-exit-codes with zizmor, since its severity-graded exit codes make a naive non-zero check unreliable.

What is the difference between an SBOM and an ABOM?▼

An SBOM inventories components that ship in the product, while an Action Bill of Materials inventories third-party code that influences the build: actions, reusable workflows, container images, and build tools. The skill generates ABOMs bound to a source revision with generate_action_bom.py.

Does keyless cosign verification work without identity constraints?▼

No. Keyless cosign verification requires --certificate-identity or --certificate-identity-regexp plus --certificate-oidc-issuer. An over-broad regexp like .* verifies successfully but only proves somebody with a Sigstore identity signed the image, so anchor the pattern to the org, repo, and workflow.

When should I not use this supply chain skill?▼

Do not use it for application code vulnerabilities, which belong to a repository audit or diff review, or for LLM, agent, and MCP risks. It focuses on workflows, dependency intake, release pipelines, and compliance obligations.

How do release cooldowns protect against malicious npm packages?▼

Most malicious releases are yanked within hours, so delaying adoption filters them without review. npm CLI 11.10.0 added min-release-age in days with min-release-age-exclude for exceptions, and Renovate offers minimumReleaseAge.