Six pillars. One clear report.
This is a sample — fictional findings so you can see the report shape. Run one on your repo.
main · demo
Each finding had to survive a code review and a second pass that tries to throw false alarms out.
This is a sample Integrity Check report so you can see the six pillars and fix list before connecting GitHub. Real runs have a reviewer read the code before findings are published.
A demo API key pattern was found in config.
Demo mode returns a fake dashboard payload.
Dashboard and PDF recompute the same average separately.
No blanket cache clears spotted in the sample.
Empty states and tooltips differ across sibling lists.
The main list asks for four filters before showing Priority items.
A demo API key pattern was found in config.
src/config.tsImpact: A secret appears to be hardcoded in source.
From the code: export const apiKey = "sk-live-example-not-a-real-key";
Fix: Move secrets to environment variables and rotate the key.
Demo mode returns a fake dashboard payload.
src/api/dashboard.tsImpact: Demo users may see numbers that live never produces.
Fix: Seed real data and use the same API for demo and live.
Dashboard and PDF recompute the same average separately.
src/pages/Dashboard.tsxImpact: Two screens can disagree on the same metric.
Fix: Compute once on the server; both screens read that result.
No blanket cache clears spotted in the sample.
No findings for this pillar.
Empty states and tooltips differ across sibling lists.
src/components/Impact: Lists feel like different products.
Fix: One EmptyState and one Tooltip pattern for every list.
The main list asks for four filters before showing Priority items.
src/pages/Teachers.tsxImpact: Leaders must remember filters to see what needs attention.
Fix: Default to Priority; keep a short search.
Paste into Cursor or another coding agent. Prefer one finding at a time unless you are ready for the full list.