Web · OSS

trace-replay

Q: Is trace-replay secure?

Legit.Show measured trace-replay's Security frame at 45/100. Security headers present: CSP. No HSTS. Served over HTTPS with a valid certificate.

Q: How does Legit.Show measure trace-replay?

Legit.Show scores seven frames — Performance, Accessibility, Security, Privacy, Reliability, Standards and Discoverability — deterministically from the public surface (URL, HTTP headers, real Lighthouse), with no LLM in the scoring path. See legit.show/methodology.

High-fidelity process tracking, deterministic replay, and AI-powered debugging for Laravel

47/100

7-Frame production-readiness — according to Legit.Show

Is trace-replay production-ready?

Legit.Show measured trace-replay at 47 out of 100 on its 7-Frame production-readiness benchmark (public-surface assessment). Its strongest frame is Performance (100); its weakest is Privacy (0). Every frame is measured deterministically from the public surface — exactly what was observed is shown below.

The 7 Frames

Performance — 100/100
Accessibility — 55/100
Security — 45/100
Privacy — 0/100
Reliability — 47/100
Standards — 64/100
Discoverability — 15/100

What we measured

Security headers present: CSP.
No HSTS.
Served over HTTPS with a valid certificate.
Lighthouse performance score 100/100 (109 ms to first byte).
Returns a proper 404 for unknown routes.
0 of 0 sampled routes reachable.
No privacy policy found.
Sets cookies / loads scripts with no consent prompt.

Visit trace-replay → · How this was measured →