Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Dependency Risk Scanner — Find Vulnerable Libraries

    1

    Review resolved dependencies and advisory evidence, separate vulnerability from reachability and plan safe remediation with validation.

    $9.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Dependency Risk Scanner — Find Vulnerable Libraries

    Dependency Risk Scanner — Find Vulnerable Libraries

    Example session with this skill installed

    Illustrative scenario: Review a synthetic scanner export. Package example-lib is resolved to 1.2 in the lockfile; scanner says advisory DEMO-1 affects it and suggests 1.3. The manifest allows 1.x. Advisory text, provenance, runtime reachability and compatibility tests are absent. Produce a defensive triage plan without calling this a verified real CVE.

    • Read your context and instructions
    • Compiled the dependency risk scanner

    Dependency triage brief — illustrative synthetic advisory

    Inventory: supplied lockfile resolves example-lib 1.2; manifest 1.x is a declared range, not proof of installed version. DEMO-1 is synthetic scanner evidence for this example, not a real verified CVE.

    Finding status: reported match requiring advisory/source verification. Confirm ecosystem, exact resolved artifact, dependency path, runtime/build use and any fork/backport. No CVSS or exploitability invented.

    Context gaps: advisory affected/fixed versions and prerequisites; authenticity/provenance; reachability of affected code; exposure and asset criticality; compensating controls. Absence of reachability evidence does not prove unreachable.

    Remediation hypothesis: 1.3 may be a candidate because the supplied scanner suggests it, but verify authoritative fix information and compatibility before selection. Do not infer that the manifest range automatically updates the deployed artifact.

    Safe plan: retain reproducible current state; verify advisory and release notes; evaluate direct/transitive path; test the supported upgrade in a controlled branch/environment; run appropriate behavioral/security checks; inspect resolved lockfile/build output; prepare rollback and staged release under actual policy.

    Release decision: authorized engineering/security owners weigh confirmed severity, exposure, exploit evidence, fix feasibility and business risk. Current priority is evidence completion; no production-safe verdict.

    Execution notes: no registry or repository accessed, scan run, package upgraded, exploit attempted or remediation confirmed.

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

    About this skill

    Dependency Risk Scanner supports authorized defensive software-composition analysis from manifests, lockfiles, SBOMs, build artifacts and scanner exports. It establishes the actual package inventory and resolved versions before assessing advisories, provenance, transitive dependencies or release priority.

    Its DEPRISK-360 workflow distinguishes known vulnerability status, reachability, exploit prerequisites, exposure and business impact. Runtime and build-time risks differ, and compensating controls and fix availability inform priority. Upgrades need compatibility checks, reproducibility, tests and rollback rather than blind major-version replacement.

    Current advisories require genuine authoritative sources or verified exports; old software is not automatically vulnerable and a clean report is not proof of security. It never invents CVEs, scores, package versions, scanner results or upgrade success, and does not support unauthorized exploitation.

    Known-advisory scans cannot detect all risk. Databases may be incomplete or delayed; forks, backports and dynamic reachability complicate matching. A clean report does not prove security. Cannot guarantee compatibility, absence of compromise or compliance.

    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 1 month ago

    Permissions

    Read Files
    Write Files

    File Scopes

    Authorized
    task
    inputs
    and
    agreed
    output
    directory
    only

    Authorized defensive assessment only. Optional read/write files support manifests, sanitized exports and reports. No secrets, repository access, package installation, scanner execution or production upgrade assumed. Tools and external actions require explicit authorization; avoid operational exploitation guidance.

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    No. It prioritizes resolved lockfile/build versions and the actual dependency path before advisory matching.

    No. Observable and known risk is only part of software security; provenance, support and context also matter.

    It prepares a safe remediation plan. Installation or releases require authorization and compatibility, validation and rollback checks.

    New in Security