More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Composer Package Safety Check

    1

    This skill finds those and six other Composer mistakes before your next install, and tells you how to fix each one.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Composer Package Safety Check

    Composer Package Safety Check

    Example session with this skill installed

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

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

    $ python3 scripts/check_composer.py examples/risky
    BLOCK auth.json:5 K01 AUTH_FILE_WITH_TOKENS
    "password": "<redacted>"
    Why: auth.json holds Composer credentials (GitHub, GitLab or Bitbucket tokens, http-basic passwords or bearer tokens) and is not ignored by git. Anyone with the repository can use them to read your private packages, and often your private repositories too.
    Safer: Add auth.json to .gitignore, remove it from the repository and its history, revoke the tokens, and pass credentials with the COMPOSER_AUTH environment variable in CI.

    BLOCK composer.json:16 K02 INSECURE_PACKAGE_SOURCE
    BLOCK composer.json:21 K02 INSECURE_PACKAGE_SOURCE
    BLOCK composer.json:23 K03 TOKEN_IN_COMPOSER_JSON
    REVIEW composer.json K14 NO_LOCK_FILE
    REVIEW composer.json:7 K13 UNPINNED_DEPENDENCY
    REVIEW composer.json:8 K16 DEBUG_PACKAGE_IN_PRODUCTION
    REVIEW composer.json:17 K15 NON_CANONICAL_REPOSITORY
    REVIEW composer.json:25 K12 ALL_PLUGINS_ALLOWED
    REVIEW composer.json:30 K11 SCRIPT_RUNS_DOWNLOADED_CODE
    REVIEW composer.json:33 K13 UNPINNED_DEPENDENCY

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

    BLOCK auth.json

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

    About this skill

    A committed auth.json hands out your private-package tokens, secure-http false lets anyone on the network swap a package, and laravel-debugbar in require ships a debug panel to production. This skill finds those and six other Composer mistakes before your next install, and tells you how to fix each one.

    Your agent runs a scanner on composer.json, composer.lock and Composer's auth.json. It knows Composer's own rules: php and ext-* lines are platform requirements, Composer 2 repositories are canonical by default, and the default package type is library. It reads .gitignore so an ignored auth.json is not reported. It never runs Composer or downloads anything. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Tokens are never printed.

    What it checks

    BLOCK

    • K01: an auth.json with tokens or passwords that git does not ignore
    • K02: secure-http false, disable-tls, or http:// and git:// package sources
    • K03: tokens or passwords written in composer.json

    REVIEW

    • K11: Composer scripts that download and run code
    • K12: allow-plugins set to true
    • K13: *, open-ended or dev-branch versions, or minimum-stability dev
    • K14: a project without composer.lock
    • K15: repositories with canonical false (dependency confusion)
    • K16: debug and test tools in require instead of require-dev

    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 each file as written: known vulnerabilities in package versions (use composer audit), the global Composer config, COMPOSER_AUTH and what plugins do are not checked. NOT FLAGGED is not a guarantee.

    Static check of composer.json, composer.lock and auth.json. Package vulnerabilities and global Composer settings are not checked. 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

    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 clearly fake, inert tokens (not-a-real-...) for the scanner to find. Nothing is run.

    Listed7 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 composer.json, composer.lock and auth.json as text. It never runs Composer or downloads packages.

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

    New in Security