Readiness score
62 / 100
Sample report
Generated: June 2026
This report was generated from fictional source code for demonstration purposes. Clipboard.ai is not a real company and no real product was analyzed.
This is a sample report generated from fictional data. No real code or product was analyzed.
Readiness score
62 / 100
Risk tier
Medium
Evidence confidence
74%
CRITICALExposed .env credentials in git history
Scanner: Gitleaks · File: .env · Line: 1 · API keys are recoverable from commit history.
HIGHNo authentication rate limiting on /api/login
Scanner: Semgrep · Missing request throttling creates predictable brute-force risk.
MEDIUMMissing CORS policy — all origins accepted
Static analysis · Global allowlist fallback to "*" increases data exposure risk.
| Claim | Status | Evidence |
|---|---|---|
| Uses JWT authentication | ✅ Supported | auth.ts:47 |
| No third-party data sharing | ❌ Unsupported | No privacy policy found |
| GDPR compliant | ⚠️ Insufficient evidence | No DPIA / process controls located |
4 of 7 expected files present (missing: privacy policy, SECURITY.md, deployment docs)
Add rate limiting: `npm install express-rate-limit` → add to /api/loginRotate leaked credentials immediately, add `.env` to `.gitignore`Run a real review with your codebase, scan findings, and get a complete Launch Passport.
Run your scan →