More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Shopify App Safety Check

    1

    A webhook route that never checks X-Shopify-Hmac-Sha256 accepts fake orders/create and customers/redact events from anyone who finds the URL.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Shopify App Safety Check

    Shopify App Safety Check

    Example session with this skill installed

    Check this project with shopify-app-safety-check.

    • Read your context and instructions
    • Compiled the shopify app safety

    $ python3 scripts/check_shopify.py examples/risky
    BLOCK app/shopify.server.ts:9 H01 SHOPIFY_SECRET_IN_CODE
    apiSecretKey: process.env.SHOPIFY_API_SECRET || "<redacted>",
    Why: A Shopify token (shpat_, shpca_ or shppa_ access tokens, shprt_ refresh tokens, shptka_ Theme Access passwords), the app's client secret (shpss_, SHOPIFY_API_SECRET, apiSecretKey) or a private Storefront token is written in a code, config or env file that git would commit, or as a literal fallback for an env variable. Anyone who can read the repository, a build log or a shipped bundle can call the Admin API as your app with every scope the token has, or forge webhooks and app proxy requests with the secret.
    Safer: Load secrets from environment variables or a secret manager with no literal fallback and keep .env files out of git. Deleting the line later does not remove it from git history, so rotate what was committed: create a new client secret in the Dev Dashboard and replace stored tokens, and revoke or reissue exposed tokens.

    BLOCK web/.env.production:4 H04 ADMIN_SECRET_IN_PUBLIC_ENV
    BLOCK web/server.js:12 H02 WEBHOOK_HMAC_NOT_VERIFIED
    BLOCK web/server.js:23 H03 APP_PROXY_SIGNATURE_NOT_VERIFIED
    BLOCK web/server.js:44 H01 SHOPIFY_SECRET_IN_CODE
    REVIEW app/shopify.server.ts:10 H13 UNSUPPORTED_API_VERSION
    REVIEW extensions/points-banner/shopify.extension.toml:1 H13 UNSUPPORTED_API_VERSION
    REVIEW shopify.app.toml:4 H15 DEV_URL_IN_APP_CONFIG
    REVIEW shopify.app.toml:8 H12 RESTRICTED_SCOPE
    REVIEW shopify.app.toml:8 H19 SCRIPT_TAGS_DEPRECATED
    REVIEW shopify.app.toml:9 H14 LEGACY_INSTALL_FLOW
    REVIEW shopify.app.toml:12 H15 DEV_URL_IN_APP_CONFIG
    REVIEW shopify.app.toml:14 H11 COMPLIANCE_WEBHOOKS_MISSING
    REVIEW shopify.app.toml:15 H13 UNSUPPORTED_API_VERSION
    REVIEW shopify.app.toml:26 H15 DEV_URL_IN_APP_CONFIG
    REVIEW web/routes/orders.js:8 H16 REQUEST_CHECK_NOT_SEEN
    REVIEW web/server.js:30 H18 OAUTH_CALLBACK_NOT_CHECKED
    REVIEW web/server.js:52 H19 SCRIPT_TAGS_DEPRECATED
    REVIEW web/verify.js:8 H17 WEAK_HMAC_CHECK
    REVIEW web/verify.js:10 H17 WEAK_HMAC_CHECK

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

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

    About this skill

    An app proxy route that reads logged_in_customer_id but never checks the signature parameter lets anyone call it directly and read another customer's points, wishlist or orders. A webhook route that never checks X-Shopify-Hmac-Sha256 accepts fake orders/create and customers/redact events from anyone who finds the URL. A VITE_SHOPIFY_ADMIN_API_TOKEN ships your Admin token to every visitor. This skill finds those and ten other Shopify app mistakes before you deploy, and tells you how to fix each one.

    Your agent runs a scanner on shopify.app.toml and shopify.app.*.toml, shopify.extension.toml and shopify.theme.toml, .env files, Shopify config YAML and JSON (for token prefixes), and JavaScript, TypeScript, Python, Ruby and PHP code that mentions Shopify (React Router and Remix templates, Express, Next.js, Flask, Rails, Laravel). It knows what the official libraries verify for you (authenticate.webhook, authenticate.public.appProxy, shopify.webhooks.validate, processWebhooks, validateHmac with the appProxy signator, ShopifyApp::WebhookVerification and AppProxyVerification, PHP Registry::process, the older Shopify.Webhooks.Registry.process and Koa receiveWebhook), says REVIEW instead of BLOCK when a check may live in middleware or a router it cannot read, and in a folder scan follows a verifying helper defined in another file, whether it is called, passed as route middleware or used as a decorator. It checks API versions against Shopify's 12-month support window using the date of the scan. It reads .gitignore, so a secret in a .env file that git ignores is counted in one line instead of reported. Comments and test files are skipped and nothing is run or sent to Shopify. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Tokens and secrets are never printed.

    What it checks

    BLOCK

    • H01: shpat_, shpca_, shppa_, shpss_, shprt_ or shptka_ tokens, client secrets and Admin or private Storefront tokens written in code, config or env files git would commit (JavaScript, TypeScript, Python, Ruby and PHP forms), including literal fallbacks for env variables
    • H02: a file that builds the whole request path and handles Shopify webhooks with nothing that checks X-Shopify-Hmac-Sha256
    • H03: the same for app proxy handlers that never check the signature parameter
    • H04: Admin tokens, private Storefront tokens or the client secret in browser-exposed variables (NEXT_PUBLIC_, VITE_, PUBLIC_, REACT_APP_, EXPO_PUBLIC_ and others)

    REVIEW

    • H11: a production app config that does not subscribe to all three mandatory compliance webhooks while the app lists some of them, handles one in code or declares App Store distribution (the template default, which the finding names)
    • H12: restricted or approval-only scopes: read_all_orders, write_themes, read_users, payment mandate, gateway and session scopes, read_customer_payment_methods, own subscription contract scopes
    • H13: Admin, Storefront or webhook API versions Shopify no longer supports, or unstable
    • H14: use_legacy_install_flow = true
    • H15: localhost, Cloudflare or ngrok tunnel, or plain http URLs in a deployed app config
    • H16: webhook or app proxy handlers whose signature check, if any, sits in middleware, a router or a helper the scan cannot follow
    • H17: hand-made HMAC checks that compare with == or sign re-serialized JSON instead of the raw body
    • H18: hand-made OAuth callbacks with no visible hmac, state nonce or anchored shop domain check (client credentials, token exchange and refresh-token requests are left alone)
    • H19: deprecated script tags (write_script_tags, scriptTagCreate, scriptTagUpdate, REST ScriptTag)

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason, safer approach and Shopify documentation link for each rule
    • A risky and a safe example Shopify app (app config, extension config, React Router server file, Express backend, router, helper and env file), and the real report the scanner produces on the risky one

    Limits It reads each file as written: settings made in the Dev Dashboard or Partner Dashboard, environment values and middleware or helpers outside the scanned folder are not seen. Code that never names Shopify, a Shopify header or logged_in_customer_id is not read. Liquid theme files and Go or Java apps are not checked, and YAML or JSON files are read for token prefixes only. Whether an app is listed in the App Store cannot be known from files, so the compliance check needs signs from the project. Results for API versions change as Shopify retires them. NOT FLAGGED is not a guarantee.

    Static check of Shopify app config, env and code text. Dashboard settings, environment values and checks done outside the scanned folder are not followed. 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 4 days ago

    Requires

    Python

    Permissions

    Terminal / Shell
    Read Files

    Allowed Hosts

    ${shop}

    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 credentials (NOTREAL, EXAMPLE, not-a-real) in shapes that common secret scanners do not match, for the scanner to find. Nothing is run and nothing is sent to Shopify.

    Listed4 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 shopify.app.toml, extension configs, .env files and app code as text. It never calls Shopify or your app, and tokens and secrets it finds are masked.

    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.

    New in E-commerce