Secure Deps Audit — Dependencies, Secrets & Auth

    1

    Severity-rated audit of dependencies, leaked secrets, and auth misconfig — evidence with paths, confirm before every write.

    $29

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Secure Deps Audit — Dependencies, Secrets & Auth

    Example session with this skill installed

    Run a full secure-deps-audit on this repo. Check everything: dependencies, secrets, and auth config.

    • Read your context and instructions
    • Compiled the secure deps audit

    I have completed a comprehensive security scan of the repository. The audit covered package manifests, tracked files for credential leaks, and authentication middleware patterns.

    Secure Deps Audit

    Scope: Dependencies, Secrets, Auth (Full Depth)

    Blockers

    Critical Vulnerability in axios: Severity: Blocker. Found axios@0.21.1 in package.json. CVE-2021-3749 (SSRF). Fix hint: Upgrade to ^0.21.4.

    Exposed Stripe API Key: Severity: Blocker. Evidence: src/config/stripe.ts:12 contains sk_live_51...G8kP. Fix hint: Move to .env and add to .gitignore.

    Majors

    Permissive CORS Policy: Severity: Major. Evidence: server.js:45 shows origin: '*'. Fix hint: Restrict to specific domains.

    Unpinned Git Dependency: Severity: Major. Evidence: package.json uses github:org/repo without a commit hash. Fix hint: Pin to a specific SHA.

    Minors

    Missing Secure Flag: Severity: Minor. Evidence: auth.js:22 session cookies missing secure: true. Fix hint: Enable secure flag for production environments.

    Summary

    2 blockers / 2 majors / 1 minor

    Fix plan

    1. Upgrade axios to version 0.21.4 [needs confirm]
    2. Remove hardcoded Stripe key and update .gitignore [needs confirm]
    3. Update server.js to whitelist specific origins for CORS [needs confirm]
    4. Pin the git dependency in package.json to the latest stable commit [needs confirm]

    Next steps

    • Provide confirmation to execute the dependency upgrade and file edits.
    • Immediately rotate the exposed Stripe Secret Key in your Stripe dashboard.
    • Verify if any other .env patterns are present in the git history.

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

    About this skill

    Dependency vulnerabilities and leaked secrets are silent killers in a codebase. This skill provides a systematic security audit focused on package manifests, hardcoded credentials, and authentication patterns to identify risks before they reach production.

    What it does

    • Vulnerability scanning identifies known CVEs in lockfiles using native audit tools.
    • Secrets detection flags committed environment files, high-entropy strings, and API keys.
    • Auth review analyzes code-level patterns like wide-open CORS or missing CSRF protection.
    • Supply chain analysis inspects install scripts and unpinned git dependencies for risks.
    • Remediation planning generates a prioritized fix list categorized by severity level.

    How it works

    1. Define scope by selecting surfaces like dependencies, secrets, or auth patterns.
    2. Execute scan in read-only mode to gather evidence across the repository.
    3. Review report which ranks findings from Blockers to Minors with specific file paths.
    4. Approve fixes for specific items like dependency upgrades or middleware updates.

    Frameworks & tools

    Works with package.json, pnpm-lock.yaml, requirements.txt, and other standard manifests. Interfaces with npm audit, pnpm audit, and pip-audit for advisory database lookups.

    Why this beats prompting it yourself

    Generic prompts often miss supply chain risks like postinstall scripts or fail to redact sensitive keys in their own output. This skill enforces a strict read-only discovery phase and a severity rubric to ensure critical blockers are never buried under minor linting issues.

    Use cases

    • Audit a legacy repository before starting a major refactor.
    • Scan PRs for accidentally committed .env files or hardcoded tokens.
    • Perform a supply chain check on third-party packages and install scripts.

    Known limitations

    Cannot perform full penetration testing or dynamic analysis. Offline environments or private registries may prevent fetching the latest vulnerability advisory databases.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    Cannot perform dynamic pentesting. Requires internet access for advisory DBs. User must manually rotate third-party secrets; agent only removes them from the codebase.

    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 buying a skill.

    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 24 days ago

    Software
    Cursor
    orClaude Code
    Optional
    npm
    orpnpm
    orYarn

    Permissions

    Read Files

    Terminal for package audit. Read for lockfiles and source. Write only after confirm for bumps or auth fixes. Env for detecting committed secrets without printing values.

    Listed27 days ago

    What's inside

    Frequently Asked Questions

    This skill functions as a security-focused reviewer that can be added to any AI agent with repository access, providing it with a specialized framework to identify vulnerabilities that general-purpose coding agents often overlook.

    No, the skill operates in a read-only discovery mode to identify risks. While it provides a prioritized remediation plan, it will only apply dependency upgrades or code fixes if you explicitly review and approve the suggested changes.

    The skill supports major package managers including npm, pnpm, and pip, and it is designed to detect hardcoded secrets and auth patterns across most common web development frameworks.

    Your purchase includes the full skill configuration, the severity-ranked reporting logic, and a standardized rubric for evaluating supply chain risks like unpinned dependencies or malicious install scripts.

    While the skill is highly effective at identifying known CVEs and static secrets, it cannot perform dynamic runtime analysis or active penetration testing; for the most accurate results, it requires an internet connection to fetch the latest vulnerability advisory databases.

    New in Security