Notre avis

Analyse les dépendances d'un projet pour détecter les vulnérabilités, générer des SBOM et proposer des stratégies de remédiation.

Points forts

Prise en charge multi-écosystèmes (npm, pip, Maven, etc.)
Génération de SBOM pour la conformité
Identification des risques de licence et des dépendances obsolètes

Limites

Nécessite un fichier manifeste ou lockfile
Ne couvre pas les tests de sécurité runtime
Les correctifs automatiques nécessitent une approbation manuelle

Quand l'utiliser

Pour auditer les dépendances d'un projet avant une release ou dans le cadre d'une politique de sécurité.

Quand l'éviter

Lorsque l'environnement ne fournit pas de manifeste de dépendances ou si le besoin porte sur des tests de sécurité en production.

Exemples

Scan project dependencies for vulnerabilities

Scan the dependencies of this project for known vulnerabilities using OWASP Dependency-Check or Snyk. List any critical or high-severity issues and suggest remediation steps.

Generate an SBOM for compliance

Generate a Software Bill of Materials (SBOM) in SPDX or CycloneDX format for this project. Include all direct and transitive dependencies with their versions and licenses.

Audit outdated packages and license risks

Audit the package.json and requirements.txt for outdated dependencies and license compliance issues. Provide a report with recommended version upgrades and license conflicts.

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 ecosystems to identify vulnerabilities, ass... category: Security & Systems source: antigravity tags: [ai, security, vulnerability, cro] url: https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/security-scanning-security-dependencies

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.

Analyse des vulnérabilités de dépendances

Recommandé pour