WITNESS ENGINE
Know what changed before it ships.
WITNESS learns your application's behavior and catches dangerous changes before they ship.
Local-first, evidence-first, and authorization-gated. WITNESS does not guess permission or fabricate authentication.
5-minute first scan path
A focused first-run journey: install the CLI, prove control of a staging target, run a bounded safe scan, then inspect and verify the evidence.
1
Install
npm install @witness-engine/cli
2
Prove control
Use an origin-scoped verification grant.
3
Scan safely
Run Full, Focus, or Change Scan with bounded actions.
4
Audit & verify
Open report.html and verify the evidence chain.
The five-minute path is an onboarding target, not a universal timing guarantee; target size and browser setup can change runtime.
Authenticated WITNESS runtime proof
Loading authenticated proofβ¦
β
π Pages Safely Explored
β
β‘ Business Actions Inventoried
β
π Safe State Transitions
β
π Confirmed Findings
- Confirmed Findings
- β β β Medium / β Low / β High
- π§ Business-Truth Checks
- β
- π‘οΈ Business-Truth Contradictions Observed
- β
The wording above reflects the evidence recorded in the supplied run.
π― Single Critical Workflow Proof
Loading workflow proofβ¦
β
Publisher signature was verified during the Vercel build before this artifact was deployed.
π Cryptographic Provenance
- π Authorization: Authorized local-repository run
- β
Evidence Chain: Valid
- π Publisher Authenticity: Ed25519 signature verified
- π§Ύ Evidence Integrity Boundary: SHA-256 digest verified
Waiting for public proof feed.