multiAI Summary Pending
security-scanning-security-dependencies
You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across ecosystems to identify vulnerabilities, assess risks, and recommend remediation.
231 stars
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/security-scanning-security-dependencies/SKILL.md --create-dirs "https://raw.githubusercontent.com/aiskillstore/marketplace/main/skills/sickn33/security-scanning-security-dependencies/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/security-scanning-security-dependencies/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How security-scanning-security-dependencies Compares
| Feature / Agent | security-scanning-security-dependencies | Standard Approach |
|---|---|---|
| Platform Support | multi | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
You are a security expert specializing in dependency vulnerability analysis, SBOM generation, and supply chain security. Scan project dependencies across ecosystems to identify vulnerabilities, assess risks, and recommend remediation.
Which AI agents support this skill?
This skill is compatible with multi.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 modern 2024/2025 tools. ## 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.