Skip to content
ShipShield

ShipShield Secure-to-Ship Standard

Version 1.0, published 18 October 2026; certificate contents clarified 7 November 2026 (pass criteria unchanged). These are the criteria an app must meet to display the ShipShield Certified™ mark. Certificates are issued from the ShipShield dashboard on the Pro and Agency plans, and anyone can check one on the verification page.

What the mark means

The mark means an app met these automated criteria on the dates shown on its certificate. It is not a guarantee that the app is secure, free of vulnerabilities or legally compliant. Automated pattern checks can miss problems that need human review, data-flow analysis or tests of signed-in pages.

1. Scope

The standard applies to web and mobile apps, including apps built with AI code generators. A certification scan covers:

A scan of pasted code alone cannot earn the mark.

2. Pass criteria

One certification scan must meet every criterion.

#CriterionPass when
1Ship verdictThe verdict is “Ready to ship”.
2Critical and high code findingsNone, across ShipShield's security rules: exposed keys, private keys, Supabase service-role keys in front-end code, row-level security switched off, open Firebase rules, SQL injection, eval and shell injection, weak hashing, weak JWT secrets, cross-site scripting, unprotected admin routes and committed .env secrets.
3Security score85 or higher out of 100.
4Compliance score60 or higher out of 100.
5Legal basicsThe live site has a privacy policy, terms of service and, where it uses non-essential cookies, a cookie consent control.
6Live site and pen testNo critical or high pen-test finding, and a valid TLS certificate.
7DependenciesNo known critical or high vulnerability in a declared dependency, according to OSV.dev on the scan date.
8Applicant attestationA named person at the applicant confirms the scan covered the production code and site, and accepts the mark-use rules.

3. Certificate and verification

Each certificate names the app, its verified domain, the repository and commit that were scanned, the standard version, and the issue and expiry dates. A private repository's name is shown only to its owner; the public page shows the commit. It is valid for 90 days and signed by ShipShield. Anyone can check a badge on its public verification page, which shows whether it is valid, expired, suspended or revoked.

4. Staying certified

5. Suspension and revocation

6. Equal access

Any app that meets this standard is certified, whoever owns it. We do not refuse certification for any other reason, and every applicant pays the same published prices.

7. Changes to the standard

A new version is published here at least 30 days before it takes effect. Certificates issued under an earlier version stay valid until they expire.