Free
$0
- Daily theme and app embed scan
- Daily shopper walk to cart and checkout
- Store data, app embed and pixel change checks
- PCI DSS 6.4.3 and 11.6.1 script report
- Email and team chat alerts, scan history and CSV export
- No billing through Shopify
Custos: Store Security Scan Live
Shopify app that scans your theme for code patterns used by card skimmers and walks your store like a shopper, for shops that want to know which code runs at checkout.
A daily shopper walk records every script, app embed and pixel, compares them with the baseline you trusted and flags what changed.
On the Shopify App Store
| Severity | Finding | First seen |
|---|---|---|
| High | New script from cdn.example-widgets.net on product pages | 11 Nov |
| Medium | App embed turned on in your live theme | 10 Nov |
| Low | Web pixel sends events to a new site: collect.example.net | 9 Nov |
Try it here
Pick what changed on the store since the last scan and see the findings, the script inventory and the alert it sends.
A sample store, scanned on 11 November 2026 against the baseline it trusted on 3 November. The sites are made-up examples.
No new findings. Everything the walk saw matches the baseline you trusted on 3 November.
| Script | Site | First seen | Status |
|---|---|---|---|
| theme.js | your store | 3 Nov 2026 | Trusted |
| chat-widget.js | cdn.example-chat.com | 3 Nov 2026 | Trusted |
| Card fields frame | checkout.shopify.com | 3 Nov 2026 | Trusted |
Each script is listed with a fingerprint of its content, so the same address serving new code shows as changed.
No email: alerts go out only when a scan finds something new.
| Severity | Finding | Page |
|---|---|---|
| High | new script from cdn.example-widgets.net since 11 Nov 2026 | product |
A finding says what changed and when. If you or your team made the change, mark it as trusted; otherwise each finding has steps to fix it.
| Script | Site | First seen | Status |
|---|---|---|---|
| theme.js | your store | 3 Nov 2026 | Trusted |
| chat-widget.js | cdn.example-chat.com | 3 Nov 2026 | Trusted |
| Card fields frame | checkout.shopify.com | 3 Nov 2026 | Trusted |
| loader.min.js | cdn.example-widgets.net | 11 Nov 2026 | New |
Each script is listed with a fingerprint of its content, so the same address serving new code shows as changed.
Open the app to see each one, then trust it if you or your team made the change, or fix it. The same alert can go to Slack, Microsoft Teams or Google Chat.
| Severity | Finding | Page |
|---|---|---|
| Critical | checkout ends on pay.example-checkout.io, not your store’s domain or Shopify’s checkout | checkout |
| Medium | the chat-widget.js script now serves different content | home, product |
A finding says what changed and when. If you or your team made the change, mark it as trusted; otherwise each finding has steps to fix it.
| Script | Site | First seen | Status |
|---|---|---|---|
| theme.js | your store | 3 Nov 2026 | Trusted |
| chat-widget.js | cdn.example-chat.com | 3 Nov 2026 | Changed |
| Payment page | pay.example-checkout.io | 11 Nov 2026 | New |
Each script is listed with a fingerprint of its content, so the same address serving new code shows as changed.
Open the app to see each one, then trust it if you or your team made the change, or fix it. The same alert can go to Slack, Microsoft Teams or Google Chat.
Your theme, the apps you installed and the pixels you added all load code into your buyers’ browsers, checkout included. Apps update that code on their own servers, so what loads can change while your theme file stays the same.
Shopify lists your theme files and app embeds, but not a dated record of what actually loads when someone shops, where each script sends data or when it first appeared.
Rules for payment pages ask for the same record: PCI DSS 4.0 requirements 6.4.3 and 11.6.1 are about knowing which scripts run on payment pages and noticing when they change.
Shops that edit their theme often, run many apps and pixels, or work with outside developers, and want to see what changed and when.
A browser on the app’s server visits your store like a shopper: home, a collection, a product, search, the cart, the customer login and checkout, stopping at the payment step. It records every script, a fingerprint of its content and the sites it talks to, with a screenshot of each step. It never places an order.
The first scan is your baseline. Each later scan reports what is new, what changed and what was removed: a new script, app code that now serves different content, a new app embed, a pixel sending events to a new site, or a checkout that ends on a site that is not your store’s domain. A finding says what changed and when; mark an expected change as trusted and it joins the baseline.
The data scan reads the metafields and metaobjects your theme prints, the code files in Content › Files, URL redirects and menu links. It flags scripts and links to unknown sites in them and metafields your theme prints without escaping, with the file or key and the steps to fix it.
The full detail of each check, so you know what a clean scan means and what it does not cover.
A clean scan means nothing new was found where the app looked. It is not a certificate and not a PCI DSS assessment.
Install the app and start a scan. Look through what it found and mark it as your baseline.
Create the test customer in Settings for the account and checkout steps, and enter your storefront password if the store has one.
Later scans report only what is new, changed or removed, by email or team chat.
Knowing the limits up front saves you an install.
No tool can promise that. It reports what is new or changed in the code that reaches your buyers, and content that matches known risky patterns, and it says plainly what it could not see, such as pages the walk does not visit.
Its access is read-only, except for one tagged test customer it creates for the walk. It does not edit your theme, apps or settings, and it does not block or remove what it finds.
The walk opens checkout as a guest and stops at the payment step. It types nothing into checkout; the card fields are Shopify’s own secure frame, and the app only records which site they load from.
It keeps a dated list of the scripts on your storefront and checkout and alerts you to changes, which you can use when you review your scripts. It does not certify your store against PCI DSS or any other standard.
$0
Something else? Write to hello@reply.getstorefleet.com.
Free. There is no paid plan and no charge: every shop gets the daily theme and app embed scan, the daily shopper walk to checkout, the data, app embed and pixel checks, the PCI script report, alerts, scan history and CSV export.
Read access to your themes, products, content, metaobjects and their definitions, files and navigation, to check what your storefront shows. Read and write customers, used only to create, find and delete one tagged test customer for the walk: it reads no other customer and no orders.
No. Scans run on the app’s servers and add nothing to your theme, so shoppers see nothing.
No. The scan works on every Shopify plan. The walk needs one product that is available to buy, because Shopify does not open checkout for an empty cart.
No tool can promise that. The app reports what is new or changed in the code that reaches your buyers, and content that matches known risky patterns, such as code that listens to card fields or sends data to unknown sites. A finding is not a verdict that an app or a person is harmful: most changes come from your own theme edits or app updates.
Scans stop at once and Shopify ends the app’s access. 48 hours later Shopify asks the app to erase your store’s data, and it deletes your scans, findings, recordings and settings. The test customer stays in your store until you delete it.
Step-by-step articles on the job this app does.
A Shopify store security checklist for merchants: sign-in and staff access, apps, theme code, scripts and pixels, checkout, domain and email, and a routine to repeat.
Signs of an injected script or card skimming on a Shopify store, where such code hides, how to inspect your theme step by step, and what to do when you find it.
What PCI DSS 6.4.3 and 11.6.1 ask for, what Shopify covers as a Level 1 provider, what stays with you after the SAQ A change, and how to keep a script inventory.
Install it, run the first scan and look through the scripts, app embeds and pixels it finds.