Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Dependency vulnerability auditor

    1

    Audits project dependencies for CVEs, license compliance risks, and supply-chain attacks.

    $1.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Dependency vulnerability auditor

    Dependency vulnerability auditor

    Example session with this skill installed

    I am adding 'lodahs' to my package.json for a commercial web app. Can you check if this is safe? Here is the file: {"dependencies": {"lodahs": "^4.17.21"}}

    • Read your context and instructions
    • Compiled the dependency vulnerability auditor

    WARNING: 'lodahs' is a known typosquatting pattern for the popular 'lodash' library. This is a high-risk supply-chain red flag. Additionally, without a lockfile, the exact version resolved is non-deterministic. Recommendation: Remove 'lodahs' and install the official 'lodash' package instead.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    Dependency audits usually return a wall of version numbers without actual risk context. Developers often miss legal landmines like copyleft licenses or supply-chain red flags that haven't triggered a CVE yet.

    What it does

    • Analyzes package.json, requirements.txt, Gemfile, and go.mod files for security gaps.
    • Identifies license contamination risks, specifically flagging AGPL/GPL dependencies in commercial projects.
    • Detects supply-chain red flags such as typosquatting patterns and suspicious postinstall scripts.
    • Prioritizes vulnerabilities based on reachability and fix availability rather than just severity scores.

    Frameworks & tools

    Supports Node.js (npm, yarn, pnpm), Python (pip, poetry), Ruby (Bundler), and Go. Integrates with osv-scanner, npm audit, and pip-audit output.

    Why this beats prompting it yourself

    General LLMs often hallucinate CVE numbers or provide outdated vulnerability data. This skill follows a strict protocol to use authoritative local tools and focuses on structural risks, like license shifts and mutable git dependencies, that basic prompts overlook.

    Use cases

    • Reviewing a pull request that adds new, unfamiliar third-party packages.
    • Performing a license compliance sweep before a commercial product release.
    • Investigating suspicious package behavior or potential typosquatting.
    • Hardening supply-chain security by moving from branch-based to SHA-based pins.

    Known limitations

    Cannot perform live registry lookups. Analysis accuracy is significantly lower if a lockfile is not provided alongside the manifest.

    Requires a lockfile for precise version analysis. Cannot perform real-time network lookups to check the latest registry state.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    Read Files
    Listed2 months ago
    Updated23 days ago

    What's inside

    Frequently Asked Questions

    This skill performs a multi-layered analysis that covers known CVEs, license compliance (like flagging AGPL/GPL risks), and supply-chain anomalies such as typosquatting or suspicious install scripts. Unlike basic tools, it prioritizes issues based on reachability and provides actionable remediation steps rather than just a list of version numbers.

    The skill is compatible with Node.js (npm, yarn, pnpm), Python (pip, poetry), Ruby (Bundler), and Go projects. It is designed to work seamlessly with any AI agent capable of file access and tool execution, such as those built on AutoGPT, LangChain, or Open Interpreter.

    For the most accurate results, you should provide both the manifest file (e.g., package.json) and the corresponding lockfile (e.g., package-lock.json). The lockfile allows the skill to verify the exact dependency tree and specific versions actually installed in your environment.

    The skill is built to interface with authoritative local security scanners to ensure the vulnerability data is current and verified. This prevents the "hallucinations" common in general LLM prompts where agents might invent CVE IDs or miss recent patches.

    You will receive the core skill logic, configuration templates for various package managers, and a set of instructions for integrating it into your AI agent's workflow. It also includes pre-defined risk priority schemas to help your agent categorize findings by urgency.

    New in Security