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:
- the app's full source repository on its default branch;
- its dependency manifests;
- its live production site, on a domain whose ownership the applicant has verified;
- ShipShield's non-destructive automated pen test of that site.
A scan of pasted code alone cannot earn the mark.
2. Pass criteria
One certification scan must meet every criterion.
| # | Criterion | Pass when |
|---|---|---|
| 1 | Ship verdict | The verdict is “Ready to ship”. |
| 2 | Critical and high code findings | None, 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. |
| 3 | Security score | 85 or higher out of 100. |
| 4 | Compliance score | 60 or higher out of 100. |
| 5 | Legal basics | The live site has a privacy policy, terms of service and, where it uses non-essential cookies, a cookie consent control. |
| 6 | Live site and pen test | No critical or high pen-test finding, and a valid TLS certificate. |
| 7 | Dependencies | No known critical or high vulnerability in a declared dependency, according to OSV.dev on the scan date. |
| 8 | Applicant attestation | A 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
- Weekly rescans. Certified apps are rescanned every week.
- New problems. A rescan that finds a new critical or high issue starts a 14-day fix period. If it is not fixed in time, the certificate is suspended until a passing scan.
- Renewal. A passing scan within 90 days of issue renews the certificate for another 90 days.
5. Suspension and revocation
- Suspension: a new critical or high issue left unfixed after 14 days, a failed or lapsed domain verification, or a lapsed subscription.
- Revocation: misuse of the mark, falsified scan inputs, or certifying code other than what runs in production.
- Appeals: ask for a manual review within 30 days at contact@cloudonesoftware.com. We answer within 10 business days.
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.