Run an approved scope
Prepare disposable actors and resources. Inspect a dry-run plan before your local runner makes requests.
See the initial check packAccess regression checks for CompanyNerve apps
Your agent changed the code.
Check who can still get in.
Can the wrong workspace read your data? Can a free account call your paid feature? Run supported checks on your machine and keep the evidence of what failed, passed, or remains unverified.
Node.js 24. No signup or payment for local checks. Credentials stay local.
launchproof / reportOpen full sample
staging / Example application
Required checks failed.
Blocked for declared scope- Passed
- 1
- Failed
- 1
- Unverified
- 1
3 required checks in this declared scope. This report is not a security certification.
PassAnonymous private project access
FailCross-organization project access
InconclusiveFree access to paid project report
A failed check should tell you
what to do next.
LaunchProof records the expected behavior, the observation, and a reproducible next step. A missing fixture stays unverified. A waiver never turns a failure green.
Keep the evidence
Review the redacted JSON locally. Upload it explicitly to an application in your reporting workspace.
Create an applicationFix, rerun, compare
Export a safe handoff for your coding agent. Compare matching cases after a fix. Skipped checks remain unverified.
Inspect a findingA precise starting point.
The initial pack covers anonymous private reads, cross-workspace reads, and free-account access to a declared paid feature on the CompanyNerve adapter.
It needs authorized fixture accounts and a successful permitted baseline. A public URL alone is not enough.
Start small. Keep a useful regression check.
Try the synthetic demo, then check anonymous access to one private project.
Need help choosing fixtures or interpreting a finding? Discuss a scoped assisted review.