detecting-supply-chain-attacks-in-ci-cd
SolidScans GitHub Actions workflows and CI/CD pipeline configurations for supply chain attack vectors including unpinned actions, script injection via expressions, dependency confusion, and secrets exposure. Uses PyGithub and YAML parsing for automated audit. Use when hardening CI/CD pipelines or investigating compromised build systems.
Install
Quality Score: 92/100
Skill Content
Details
- Author
- mukul975
- Repository
- mukul975/Anthropic-Cybersecurity-Skills
- Created
- 8 months ago
- Last Updated
- 2 months ago
- Language
- Python
- License
- Apache-2.0
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
github-actions-supply-chain
Use when reviewing GitHub Actions workflow files for security issues, hardening CI pipelines, or assessing supply chain risk in a repository that uses GitHub Actions
cicd-supply-chain
Use when attacking or auditing a CI/CD pipeline or software supply chain — pwn requests, poisoned pipeline execution, compromised/mutable-tag actions, dependency confusion, registry worms, runner backdoors, OIDC trust abuse, SLSA/provenance
shipcheck-ci
Audits GitHub Actions workflows for supply-chain and injection holes (actions not pinned to a commit SHA, pull_request_target that checks out the PR head, missing or write-all permissions, script injection through github.event values, secrets echoed or put on a command line, curl piped to bash, self-hosted runners on fork triggers, missing timeouts, caches and concurrency) and hardens them, explaining the attack each finding enables. Use when the user says "audit my GitHub Actions", "is my workflow secure", "pin my actions", "harden my CI", "review my workflow YAML", or "why is my pipeline slow".