Evidence EngineFind
Point it at a staging address you are allowed to test. The scan stays inside the limits you set.
Windows 11 desktop app · prelaunch
Catch staging-site failures before client handoff.
Evidence Engine is a Windows app that scans a staging site for failed pages, broken same-site links, failed images and scripts, script errors and horizontal overflow. It then gives a developer evidence to recheck, without you writing a Playwright test.
- Inspection runs on your PC. Scan records and evidence are stored locally; optional outside services are explained before use (see Privacy).
- Each suspected failure is re-tested three times before it is called Confirmed.
- Exports one pack: a client report, an audit trail and file hashes.
Illustration One finding, from check to recheck
- 01Website check
Scan a staging address you are allowed to test, from your PC.
Runs locally - 02Finding and reason
A 404 on a linked page, re-tested three times on its own address.
Confirmed · 3 of 3 re-tests - 03Evidence Pack
Report, audit trail, screenshots and a SHA-256 manifest in one zip.
Handed over - 04Developer fixes
The site's developer makes the change. Evidence Engine never edits the site.
Done by a person - 05Recheck result
One clean recheck reads Not reproduced yet; the second reads Resolved.
Resolved after two clean checks
A simplified illustration of the sequence. The outcomes named here are the ones the recorded run produced on a test site; the recording itself is the walkthrough below.
The recorded walkthrough
Watch the walkthrough
About a minute and a half of the real application scanning a test site: the scan, one finding and its reason, the Evidence Pack, the developer's fix and the recheck. Playback starts only when you press play.
Demo — scan of a test site. 83 seconds, captions on, no sound. The real application scanning a local test site that this project controls: the scan, a finding and its reason, the Evidence Pack export, the developer's fix, and the recheck.
What was shortened, and the transcript
Some waiting is cut so the film stays short. Every cut is marked on screen and in the captions:
- The scan wait is played at 3 times speed (the scan took 24 seconds in real time). A label on screen says so while it plays.
- A few screens are held a moment longer so they can be read. Nothing else is cut, sped up or reordered.
- The card before the rechecks is not part of the app. Each recheck took about 2 seconds in real time and is shown at that speed.
00:00Evidence Engine 0.2.0, build 0a8c9ca0. A scan of a local test site this project controls: up to 4 pages and 6 links, depth 1, 5 minutes.
00:00The scan runs, shown at 3 times speed. It took 24 seconds.
00:07Scan complete: two findings.
00:11Finding 1, high: a JavaScript error on the contact page, with its reason and steps.
00:18Finding 2, medium: the Q3 report page returns HTTP 404 on 3 of 3 re-tests. Confirmed.
00:28Site pages and technical audit. The scan has to be declared a staging copy or the live site first, because the same page can be right on one and wrong on the other.
00:37The site graph: the pages this scan opened and the links between them, from the start page. It shows only what the scan reached.
00:46The audit log lists every check attempted or skipped.
00:52Export the Evidence Pack: report, audit files, screenshots, SHA-256 manifest.
00:58The developer fixes the test site. Evidence Engine does not edit it.
01:03Recheck: the link loads. One clean recheck reads Not reproduced yet.
01:09A second clean recheck reads Resolved. It takes two in a row.
01:14The script error reads Not reproduced yet. Not seen again is never marked Resolved.
Find, prove, fix, recheck
The same four steps as the walkthrough. The developer makes the fix; Evidence Engine never edits the site.
Prove
The finding shows the measured reason, the pages the scan opened, and the confirmation result.
Developer fixes
The person who owns the site makes the change. Evidence Engine does not edit the site.
Recheck
Run the check again. Resolved takes two clean checks in a row.
The finding names the address, the measured reason and the steps to see it. It was re-tested three times on its own address before it was called Confirmed. Full-size capture.
The developer fixed the test site. Evidence Engine did not change it. One clean recheck reads “Not reproduced yet”; the second reads “Resolved”. Full-size capture.
Read a finding
Every finding names the address, the measured reason and the steps to see it, and says what it does not claim. This is one from the demo scan.
- 1Severity, kind, status
Medium severity, a page failure, Confirmed. Severity comes from what was observed: a 4xx response is medium.
- 2The address
The exact page, so a developer opens the same thing.
- 3The measured reason
HTTP 404 when the page is requested. Confirmed means it failed on all 3 re-tests of its own address.
- 4Steps to see it
Start address, the link the scan followed, and the result in a desktop browser.
- 5What it does not claim
The failed request is directly observed. Whether it affects a wider user flow is not assessed.
What is in the Evidence Pack
One export builds one zip for the scan you just ran. A client can read the PDF. A developer can read the audit. The manifest lists a SHA-256 hash of each file. The pack is a local record, not a compliance certificate.
evidence-report.pdffirst page, from the exported pack
evidence-report.pdfFor the client. Findings ordered high, medium, low, with coverage and what was not checked.audit.csv · audit.jsonFor the developer. Every check attempted or skipped, with the reason, and the scan's configuration.screenshots/Each screenshot, named by an evidence id that audit.json and the handoff viewer cite; the PDF shows it beside its finding. A link that was only requested, never opened as a page, has none.handoff/index.htmlAn offline viewer a recipient can open without Evidence Engine.MANIFEST-SHA256.txtA SHA-256 hash of every file, so a recipient can see whether anything changed after export.
2 findings in scan, 2 exported 16 audit rows, 16 exported 6947a113ff2c2fcd…eeb93049 README.txt 73f148e9a5e0057f…1796e43b handoff/index.html 38288ed2993ae91c…a8428fc7 evidence-report.pdf
Download the demo Evidence Pack (.zip)
240 KB, exported by the app from the scan in the film.
What it checks
Supported checks on same-origin pages, run with the limits you choose. The product page has the full list and the ceilings.
Errors and dead ends
Pages and same-site links that return an error. Timeouts, odd redirects and rate limits are reported as “unable to verify”, never as defects.
Failed loads and script errors
Images and scripts that fail to load, uncaught JavaScript exceptions and console.error messages, with secrets in the error text redacted.
Horizontal overflow
Overflow at desktop size and in a separate phone-sized browser. The phone pass revisits pages already opened.
Two optional checks stay off unless you turn them on: an automated accessibility check (axe-core) and a local visual comparison. What they do and do not claim.
Visual comparison, when you ask for it
An optional local check compares a picture of the page with one you approved earlier on this PC. A difference is something for a person to review; it is not called a defect. These pictures are a fixture example from the demo scan.
What a scan does not do
The limits are on the product page too. They are here so nobody has to look for them.
- It does not repair the site. The developer does.
- It does not cover every check. A scan stops at its page, link, depth and time limits and reports what it did not visit.
- Timeouts, unexpected redirects and rate limits are reported as unable to verify, not as defects.
- It does not submit forms, click through carts or checkouts, or crawl pages behind a login unless you sign in for that scan.
- It is not a security scanner, a load test, an SEO crawler or uptime monitoring. Scan only a site you own or are authorised to test.
Prelaunch. Checkout is not open, the 7-day trial is not open, and nothing on this site downloads the installer. This site does not take payment.
Trial and paid
Evaluate the checks on one PC with the trial limits. The paid license is one year of scanning.
Trial
7 days · no card · one Windows user on one PC
- 30 pages and 30 link checks per scan. Depth 2, 10 minutes, and a custom list of 30 addresses.
- After 7 days, new scans stop. Exports already on the PC stay readable.
Paid
$299/year · one Windows user on one PC
- 200 pages and 500 link checks per scan. Depth 10, 30 minutes, and a custom list of 200 addresses.
- One year of scanning. Exports already on the PC still open after that year ends.
What does the phone pass do?
It reopens pages already inspected at 390×844 and checks horizontal overflow only. It is not a second crawl. FAQ.
How are passwords handled?
Evidence Engine does not collect the website-login password. You enter it directly into the isolated browser. Privacy.
Where are the limits?
The ceilings, and what is left unvisited, are on the product page.
Who built this
Evidence Engine is built by Sumit Saurabh in India and sold as Evidence Engine QA. Questions go to evidenceengine.support@gmail.com.
What stays on the PC
Scans, screenshots, and Evidence Packs stay on the PC. The app has no analytics. Activation sends Lemon Squeezy the license key, an instance id, and a name built from the PC name. This site sets no cookies and loads no third-party scripts. Privacy.
Where the demo came from
Evidence behind this demo: build, scan and file details
- Application
- Evidence Engine 0.2.0, build 0a8c9ca0: the compiled application run unpackaged, in a throw-away profile
- Source
- source hash f1a384b5699c…, lockfile e887e64b3952…
- Internal test installer
- build 808e91c1, built from the same source (SHA-256 96CF56E69619C481…); it was not used for this recording
- Recorded
- 2026-10-29 16:55 UTC
- Test site
- a local site that this project controls, at http://127.0.0.1:61546; the “fix” is the test site's own server switching state
- Scan
- bounded site, up to 4 pages, 6 link targets, depth 1, 5 minutes, desktop 1280×800, phone off; scan id see audit.json
- Real times
- scan 23.9 s; each recheck about 2 s; the full recording 79 s; the film 83 s
- Sample pack
- 240 KB, SHA-256 4a28c574da71d23f…
- What the film leaves out
- the scan form and license panel (the film starts about a second after the scan was started, on the status panel); the visual-comparison example below is a separate scan
- How it was captured
- only the application window's own pixels; a seeded test license; the Save dialog answered with a fixed path; no live activation
Not shown: the installer, signing, license activation, checkout or any real customer site. The film was recorded from the unpackaged development build named above, not from a packaged installer; a later build may differ.
Look at the finding
The walkthrough shows the evidence a developer rechecks after the fix.