sca-setup
Automates the setup of dependency vulnerability scanning and Dependabot configurations for any repository.
Install
mkdir -p .claude/skills/sca-setup && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/10288" && unzip -o skill.zip -d .claude/skills/sca-setup && rm skill.zipInstalls to .claude/skills/sca-setup
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
SCA scanning setup workflow. Use when adding software composition analysis to a repository, configuring Dependabot, setting up npm audit in CI, or when a repo is missing dependency vulnerability scanning. Produces working Dependabot config and CI checks.Key capabilities
- →Detect package managers and manifests
- →Generate Dependabot configuration files
- →Add dependency audit checks to CI workflows
- →Verify security alert settings
- →Configure automated dependency updates
How it works
The workflow scans for manifest files to identify ecosystems, then generates a standardized Dependabot configuration and adds relevant audit commands like npm audit or pip-audit to CI.
Inputs & outputs
When to use sca-setup
- →Add Dependabot to a repository
- →Configure dependency vulnerability scanning
- →Set up security audit checks in CI
- →Automate dependency security monitoring
About this skill
SCA Setup
When to Use
- Repository has no dependency vulnerability scanning
- Configuring Dependabot for automated dependency updates
- Adding
npm audit,pip-audit, or similar checks to CI - After detecting missing SCA in a security audit
Prerequisites
- Read
.github/instructions/sca-scanning.instructions.mdfor SCA governance rules - Identify package managers in use (npm, yarn, pnpm, pip, poetry, go mod, cargo, etc.)
Procedure
Step 1: Detect Package Ecosystems
Scan for manifests and determine ecosystems:
package.json/package-lock.json/yarn.lock/pnpm-lock.yaml→ npmrequirements.txt/pyproject.toml/Pipfile.lock→ pipgo.mod/go.sum→ gomodCargo.toml/Cargo.lock→ cargoGemfile/Gemfile.lock→ bundlercomposer.json/composer.lock→ composerDockerfile→ docker.github/workflows/*.yml→ github-actions
Step 2: Generate Dependabot Configuration
Create .github/dependabot.yml:
version: 2
updates:
- package-ecosystem: "<ecosystem>"
directory: "/"
schedule:
interval: "weekly"
day: "monday"
open-pull-requests-limit: 10
labels:
- "dependencies"
commit-message:
prefix: "deps"
Generate one entry per detected ecosystem. Include github-actions ecosystem to keep workflow actions updated.
Step 3: Add CI Audit Check
Create or update CI workflow to include dependency audit:
npm/yarn/pnpm: Add npm audit --audit-level=high step
pip: Add pip-audit step
Go: Add govulncheck ./... step
Rust: Add cargo audit step
Step 4: Configure Security Alerts
Verify GitHub repository settings:
- Dependabot alerts enabled
- Dependabot security updates enabled
- Secret scanning enabled (if available)
If these can’t be set programmatically, report the required settings to the user.
Step 5: Verify
- Confirm
dependabot.ymlis valid YAML - Confirm CI audit step uses correct package manager commands
- Check that all detected ecosystems have Dependabot entries
References
.github/instructions/sca-scanning.instructions.md.github/instructions/security-standards.instructions.md- Dependabot docs: https://docs.github.com/en/code-security/dependabot
When not to use it
- →When repository security standards are already fully implemented
Prerequisites
Limitations
- →Requires manual verification of CI audit commands
- →Some security settings may require manual configuration if not programmatically accessible
How it compares
It provides a systematic approach to SCA setup by mapping specific package managers to their corresponding audit tools and configuration requirements.
Compared to similar skills
sca-setup side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| sca-setup (this skill) | 0 | 4mo | No flags | Beginner |
| go-vuln-remediate | 0 | 1mo | Caution | Advanced |
| secrets-management | 5 | 3mo | Review | Advanced |
| github-actions-templates | 7 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
go-vuln-remediate
infobloxopen
Run Wiz-based vulnerability scan and automatic Go module remediation for containerized Go services in the konk repository. Use when you need to build images, scan CVEs, patch vulnerable dependencies in go.mod/go.sum across konk-service and konk-provision modules, validate builds, and prepare a PR su
secrets-management
wshobson
Implement secure secrets management for CI/CD pipelines using Vault, AWS Secrets Manager, or native platform solutions. Use when handling sensitive credentials, rotating secrets, or securing CI/CD environments.
github-actions-templates
wshobson
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
dependency-auditor
alirezarezvani
Check dependencies for known vulnerabilities using npm audit, pip-audit, etc. Use when package.json or requirements.txt changes, or before deployments. Alerts on vulnerable dependencies. Triggers on dependency file changes, deployment prep, security mentions.
fix-cves
okteto
Fix all CVEs in the Okteto CLI Docker image by scanning with Trivy and updating vulnerable dependencies and binaries
sca-trivy
rohunj
Software Composition Analysis (SCA) and container vulnerability scanning using Aqua Trivy for identifying CVE vulnerabilities in dependencies, container images, IaC misconfigurations, and license compliance risks. Use when: (1) Scanning container images and filesystems for vulnerabilities and misconfigurations, (2) Analyzing dependencies for known CVEs across multiple languages (Go, Python, Node.js, Java, etc.), (3) Detecting IaC security issues in Terraform, Kubernetes, Dockerfile, (4) Integrating vulnerability scanning into CI/CD pipelines with SARIF output, (5) Generating Software Bill of Materials (SBOM) in CycloneDX or SPDX format, (6) Prioritizing remediation by CVSS score and exploitability.