security-scanning-security-dependencies — Claude Code skill
security-scanning-security-dependencies audits project dependencies for known vulnerabilities, generates SBOM files, and plans package remediation across tech stacks.
MIT 1 installs ★ 50,109 updated 2026-10-29
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-dependencies -a claude-codeWhat security-scanning-security-dependencies does
This skill guides coding agents through dependency vulnerability audits and license compliance reviews across project manifests and lockfiles. It maps third-party components against current advisory databases, helping you track supply chain risks and export SBOM files.
The workflow enforces strict boundaries around package modifications. The agent avoids auto-applying package updates without direct consent, proposing targeted fixes on separate topic branches alongside test verification. Extended guidelines reside in resources/implementation-playbook.md.
Without a manifest or lockfile present, or if scanner tools cannot run in the environment, this skill cannot perform an audit.
What it helps with
- audit dependencies and lockfiles for known security advisories
- generate SBOM artifacts for supply chain compliance
- draft targeted package upgrades in separate git branches
- verify dependency remediation with clean test runs
Example prompts for the agent
- Audit
package-lock.jsonfor security advisories and flag any high-risk components - Generate an SBOM for the project and highlight incompatible open source licenses
- Prepare a single compatible version fix for the vulnerable dependency and verify tests
How to install security-scanning-security-dependencies
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-dependencies -a claude-code2Manually: put the files in place
~/.claude/skills/security-scanning-security-dependencies/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/security-scanning-security-dependencies/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-dependencies -a codex2Manually: put the files in place
.agents/skills/security-scanning-security-dependencies/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-dependencies -a cursor2Manually: put the files in place
.cursor/skills/security-scanning-security-dependencies/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills skills/security-scanning-security-dependencies2Manually: put the files in place
.github/skills/security-scanning-security-dependencies/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-dependencies -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/security-scanning-security-dependenciesManually: put the files in place
.devin/skills/security-scanning-security-dependencies/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-dependencies -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about security-scanning-security-dependencies
How to install security-scanning-security-dependencies in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill security-scanning-security-dependencies -a claude-code in your terminal.
What does security-scanning-security-dependencies do?
It guides the agent in identifying vulnerable packages, generating SBOM reports, checking licenses, and planning isolated remediation steps.
Can the skill automatically upgrade broken packages?
No, safety rules prohibit running auto-fixes without approval because dependency upgrades directly impact production stability.
Source text
SKILL.md · MIT
--- name: security-scanning-security-dependencies description: "You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across multiple ecosystems to identify vulnerabilities, assess risks, and provide automated remediation strategies." risk: critical source: community date_added: "2026-02-27" --- # Dependency Vulnerability Scanning You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across multiple ecosystems to identify vulnerabilities, assess risks, and provide automated remediation strategies. ## Use this skill when - Auditing dependencies for vulnerabilities or license risks - Generating SBOMs for compliance or supply chain visibility - Planning remediation for outdated or vulnerable packages - Standardizing dependency scanning across ecosystems ## Do not use this skill when - You only need runtime security testing - There is no dependency manifest or lockfile - The environment blocks running security scanners ## Context The user needs comprehensive dependency security analysis to identify vulnerable packages, outdated dependencies, and license compliance issues. Focus on multi-ecosystem support, vulnerability database integration, SBOM generation, and automated remediation using the installed tool versions and current advisory database snapshot. ## Requirements $ARGUMENTS ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Safety - Avoid running auto-fix or upgrade steps without approval. - Treat dependency changes as release-impacting and test accordingly. ## Resources - `resources/implementation-playbook.md` for detailed patterns and examples. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing. ## Example For a locked npm project, capture the exact package-lock hash, npm version and advisory timestamp, distinguish scanner errors from findings, and propose one compatible fixed version in a topic branch. Re-run relevant tests and the scanner without auto-upgrading unrelated packages or claiming exploitability from a CVE match.
© sickn33 · MIT · sickn33/agentic-awesome-skills