More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    npm Package Safety Check

    1

    Check package.json and .npmrc for supply-chain risks: install scripts that download code, http dependencies, leaked registry tokens, wildcard versions, git dependencies and missing lockfiles.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    npm Package Safety Check

    npm Package Safety Check

    Example session with this skill installed

    Check this project with npm-package-safety-check.

    • Read your context and instructions
    • Compiled the npm package safety

    $ python3 scripts/check_package.py examples/risky
    BLOCK .npmrc:2 N03 TOKEN_IN_CONFIG
    //registry.npmjs.org/:_authToken=<redacted, 16 chars>
    Why: A registry or GitHub token is written in package.json or .npmrc, so anyone who can read the repository can publish or read packages as you.
    Safer: Revoke the token, then use _authToken=${NPM_TOKEN} in .npmrc and set NPM_TOKEN in the environment or CI secrets.

    BLOCK package.json:7 N01 INSTALL_SCRIPT_DOWNLOADS
    BLOCK package.json:12 N02 DEPENDENCY_OVER_HTTP
    REVIEW package.json:2 N14 APP_NOT_PRIVATE
    REVIEW package.json:9 N13 NO_LOCKFILE
    REVIEW package.json:10 N11 OPEN_VERSION_RANGE
    REVIEW package.json:11 N11 OPEN_VERSION_RANGE
    REVIEW package.json:13 N12 GIT_OR_TARBALL_DEPENDENCY
    REVIEW package.json:14 N15 LOCAL_PATH_DEPENDENCY

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 2 files, 1 with package.json content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    A registry or GitHub token is written in package.json

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

    About this skill

    A postinstall script runs on every npm install, on every developer machine and CI server. This skill flags install scripts that download code, dependencies fetched over plain http, tokens written into config, and six other package.json and .npmrc risks, and tells you how to fix each one.

    Your agent runs a scanner on the project (npm, yarn, pnpm or bun, monorepos included; node_modules is skipped). It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach.

    What it checks

    BLOCK

    • N01: a preinstall, install, postinstall or prepare script that downloads from the network
    • N02: a dependency fetched over plain http://
    • N03: an npm or GitHub token written in package.json or .npmrc

    REVIEW

    • N10: a package.json that is not valid JSON
    • N11: a *, latest, empty or open-ended (>=) version
    • N12: a git or tarball dependency
    • N13: dependencies with no lockfile
    • N14: an app not marked "private": true
    • N15: a file: or link: dependency

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason and safer approach for each rule
    • A risky and a safe example project, and the real report the scanner produces on the risky one

    Limits It reads your package files as text and does not resolve the dependency tree, so problems inside dependencies are not seen. Lockfiles are checked for presence only. NOT FLAGGED is not a guarantee.

    Does not resolve the dependency tree or read lockfile contents. NOT FLAGGED is not a guarantee.

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

    Requires

    python3 (3.9 or newer)
    Node.js

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The examples include a clearly fake, inert token (not-a-real-token) for the scanner to find.

    Listed8 days ago
    Updated4 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads package.json and .npmrc as text. It does not run npm, install packages or contact the registry.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    The scanner, a rules guide with the reason and safer approach for every rule, a risky and a safe example, and the real report the scanner prints on the risky example.

    New in Security