Evidence Gallery: the engine, run in public.

Every report below was generated by OpenThunder’s keyless deterministic engine against the public source of a well-known open-source repository: no AI model, no account, no API key. Each card shows the exact commit analyzed and the date it was generated, and each report is regenerated on a weekly schedule from the latest engine source, so this page is continuous, reproducible proof that the analysis works, not a one-time demo.

Each card shows what the engine found: modules mapped, critical flows traced, cycles and fragile zones detected. Architecture health is one structural signal among them, not a grade: large, mature systems naturally score lower, and that is not a defect.

10 repositories · last generated 2026-10-26 (UTC)

Want accuracy, not just reach? The Accuracy Benchmark runs the same keyless detectors against fixtures with a KNOWN planted issue (or a known-clean control) and publishes expected vs detected, misses and false positives included.

fastify/fastify

fastify

Fast, low-overhead Node.js web framework

282 modules mapped 2 critical flows 0 cycles 12 fragile · 5 god-files 67/100 arch health

commit 5df959f · 2026-10-26 · 11 KB
expressjs/express

express

The classic Node.js web framework

142 modules mapped 2 critical flows 0 cycles 5 fragile · 6 god-files 77/100 arch health

commit 1c6f1b0 · 2026-10-26 · 9 KB
honojs/hono

hono

Small, fast web framework for the edges

423 modules mapped 5 critical flows 3 cycles 12 fragile · 5 god-files 49/100 arch health

commit bac5c4a · 2026-10-26 · 14 KB
axios/axios

axios

Promise-based HTTP client for browser and Node.js

276 modules mapped 4 critical flows 0 cycles 12 fragile · 3 god-files 72/100 arch health

commit aa54a5e · 2026-10-26 · 12 KB
colinhacks/zod

zod

TypeScript-first schema validation

517 modules mapped 3 critical flows 1 cycle 12 fragile · 12 god-files 54/100 arch health

commit afdac65 · 2026-10-26 · 15 KB
vitejs/vite

vite

Next-generation frontend build tool

1588 modules mapped 4 critical flows 20 cycles 12 fragile · 15 god-files 30/100 arch health

commit e954a9c · 2026-10-26 · 16 KB
nestjs/nest

nest

Progressive Node.js framework for server-side apps

2087 modules mapped 6 critical flows 16 cycles 12 fragile · 15 god-files 30/100 arch health

commit af957c9 · 2026-10-26 · 20 KB
prisma/prisma

prisma

Next-generation TypeScript ORM

4000 modules mapped 5 critical flows 2 cycles 12 fragile · 15 god-files 48/100 arch health

commit f543fb4 · 2026-10-26 · 19 KB
langchain-ai/langchainjs

langchainjs

Building LLM applications in JS/TS

2231 modules mapped 6 critical flows 4 cycles 12 fragile · 15 god-files 36/100 arch health

commit 38eb4d8 · 2026-10-26 · 20 KB
vercel/next.js

next.js

The React framework for the web

4000 modules mapped 6 critical flows 5 cycles 12 fragile · 15 god-files 30/100 arch health

commit cbf49db · 2026-10-26 · 23 KB
Reproduce any of these yourself

The engine is deterministic: the same commit produces the same report. Clone the repo, run the same two commands, compare.

git clone --depth 1 https://github.com/<owner>/<repo> cd <repo> openthunder lens generate --no-narrate openthunder lens export --out report.html

Honesty notes: these are automated static-analysis reports of public source code, generated with no human curation of the findings; they are not security audits, and not an endorsement by or affiliation with any of these projects. Scores are OpenThunder’s opinionated architecture heuristics, useful for comparison and for judging the engine, not a verdict on project quality. A repository that fails to analyze is skipped, never shown broken; the skip list is recorded in manifest.json.