More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Bun Project Check

    1

    Check Bun projects before you install or deploy: http registries, tokens in bunfig.toml and .npmrc, request data in sh -c, SQL built from values, untrusted install scripts, mixed or binary lockfiles and development mode.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Bun Project Check

    Bun Project Check

    Example session with this skill installed

    Check this project with bun-project-check.

    • Read your context and instructions
    • Compiled the bun project check

    $ python3 scripts/check_bun.py examples/risky
    BLOCK bun.lock:21 B01 HTTP_REGISTRY_OR_PACKAGE_URL
    "@acme/ui": ["@acme/ui@2.0.1", "http://npm.acme.example/@acme/ui/-/ui-2.0.1.tgz", {}, "sha5...=="],
    Why: A registry or package source uses plain http:// (install.registry or install.scopes in bunfig.toml, a registry line in .npmrc, publishConfig or a dependency URL in package.json, or a URL recorded in bun.lock). Anyone on the network path can swap the package code that bun install downloads and runs, and read the registry token Bun sends with each request.
    Safer: Use https:// for every registry and package URL (Bun's default registry is https://registry.npmjs.org/), then run bun install again so bun.lock records the https URLs. Plain http is fine only for a registry on this machine, such as Verdaccio on localhost.

    BLOCK bunfig.toml:6 B01 HTTP_REGISTRY_OR_PACKAGE_URL
    BLOCK bunfig.toml:6 B02 REGISTRY_TOKEN_IN_FILE
    BLOCK src/db.ts:7 B04 SQL_BUILT_FROM_VALUES
    BLOCK src/db.ts:12 B04 SQL_BUILT_FROM_VALUES
    BLOCK src/server.ts:14 B03 SHELL_INJECTION_FROM_REQUEST
    REVIEW bunfig.toml:3 B13 BINARY_OR_UNSAVED_LOCKFILE
    REVIEW package-lock.json B12 MIXED_LOCKFILES
    REVIEW package.json:9 B14 TLS_VERIFICATION_OFF
    REVIEW package.json:19 B11 INSTALL_SCRIPTS_ALLOWED
    REVIEW scripts/sync-prices.ts:3 B14 TLS_VERIFICATION_OFF
    REVIEW src/db.ts:8 B17 SQL_PART_FROM_VARIABLE
    REVIEW src/server.ts:6 B15 DEV_ERROR_PAGE_IN_SERVER
    REVIEW src/server.ts:19 B16 SHELL_COMMAND_FROM_VARIABLE
    REVIEW src/server.ts:23 B15 DEV_ERROR_PAGE_IN_SERVER

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

    line in .npmrc, publishConfig or a dependency URL in package.json

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

    About this skill

    A registry token written into bunfig.toml goes to everyone who can read the repository, and $sh -c "convert ${file}" hands a file name from a request to a real shell: Bun Shell escapes the value for its own parsing, not for the shell you start. And because trustedDependencies replaces Bun's built-in list of trusted packages, one extra entry runs that package's install script on every machine that installs. This skill finds those and the other Bun project mistakes below before you install or deploy, and tells you how to fix each one.

    Your agent runs a scanner on bunfig.toml, .npmrc, package.json, bun.lock (and the names of bun.lockb and other lockfiles), and the TypeScript and JavaScript files that use Bun. It follows request data through variables in each file, knows which Bun Shell and SQL forms escape or bind values and which do not, leaves number arithmetic and ? placeholder lists alone, compares trustedDependencies with Bun's own default list, treats $VAR and ${VAR} references as configured, skips comments, tests and node_modules, and never runs bun or your code. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • B01: plain http:// registries, scope registries, package URLs and lockfile URLs (a registry on localhost is fine)
    • B02: registry tokens and passwords written in bunfig.toml, .npmrc, package.json scripts, URLs, code or bun.lock
    • B03: request data passed to sh -c, bash -c, bun -e, raw interpolation or Bun.spawn with sh -c, or choosing the program to run
    • B04: bun:sqlite and sql.unsafe() queries with values put into the SQL text (also SQL built in a variable and grown with +=)

    REVIEW

    • B11: trustedDependencies entries outside Bun's default trusted list, or from git, GitHub, files or URLs (not reported when install scripts are turned off in bunfig.toml or .npmrc)
    • B12: bun.lock next to an npm, Yarn or pnpm lockfile
    • B13: the binary bun.lockb, or settings that turn off the text lockfile or lockfile saving
    • B14: TLS certificate checks turned off (rejectUnauthorized: false, NODE_TLS_REJECT_UNAUTHORIZED=0)
    • B15: Bun.serve development mode written into the code, or stack traces sent to clients
    • B16: shell commands built from variables, and request data passed as command arguments
    • B17: table or column names and other SQL parts taken from variables

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason, safer approach and official Bun documentation link for each rule
    • A risky and a safe example Bun project (bunfig.toml, package.json, lockfiles and TypeScript), and the real report the scanner produces on the risky one

    Limits It reads each file on its own: request data is followed through variables inside one file, not across modules, and Bun.serve options built in another variable, Dockerfiles, CI files and the NODE_ENV of your deploy are not read. node:child_process and SQL clients other than bun:sqlite and Bun SQL are not checked. NOT FLAGGED is not a guarantee.

    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.

    Static check of config and code text. Request data is followed only inside one file, and your home-folder ~/.bunfig.toml and ~/.npmrc, Dockerfiles and CI files are not read. 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 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 5 days ago

    Software
    Git

    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 example project includes a clearly fake, inert registry token (not-a-real-...) for the scanner to find. Nothing in it is run.

    Listed5 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 bunfig.toml, package.json, bun.lock and your code as text. It never runs Bun, installs packages or starts a server.

    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 Bun project, and the real report the scanner prints on the risky example.

    New in Security