This is a worked example. Loopnote is not a real company and no repository was scanned to produce this record. It shows what a buyer sees when they check a certificate, including the states that matter most: superseded and revoked.
This certificate is authentic
Issued by Struck Code and bound to commit 9f3c1a7d84e2. Analysed 6 August 2026, under methodology MV-2026.3.
Struck code certificate· Loopnote
VC-01J9XKQ2 · commit 9f3c1a · 6 Aug 2026
0 critical · 9 high · 8 medium · 3 of 7 claims verified
What was analysed
A multi-tenant SaaS application that collects customer feedback through an embeddable widget and gives teams a dashboard to triage it, with AI-generated summaries and Slack notifications. Built in TypeScript on Next.js with Supabase and Stripe, and deployable by a new owner from its own documentation.
- Lines of code
- 34,212
- Files
- 412
- Test files
- 87
- 21% of files
- Analysed
- 6 Aug 2026
- 46 days ago
Languages, by share of code
- TypeScript71%
- SQL9%
- CSS7%
- JavaScript5%
- JSON4%
- Markdown2%
- Shell1%
- YAML1%
Dimension by dimension
Each dimension carries how many of its checks were actually assessed. A high score resting on two checks of ten is not the same thing as a high score resting on ten, and it says so.
- Claims and functionality54 / 100 · C-
Do the advertised features actually exist in the code10 of 10 checks assessed
- Security70 / 100 · B
Can someone reach data or money they should not20 of 20 checks assessed
- Billing integrity80 / 100 · A-
Does the paywall actually hold10 of 10 checks assessed
- Code quality and maintainability73 / 100 · B
How hard will this be to work on12 of 12 checks assessed
- Tests and CI55 / 100 · C
Can you change it without breaking it8 of 8 checks assessed
- Dependencies, licensing and IP80 / 100 · A-
Can this be sold and kept running10 of 10 checks assessed
- Operability and transferability65 / 100 · B-
Can a new owner run it without the founder13 of 13 checks assessed
- Provenance and bus factor85 / 100 · A
Where did this code come from9 of 9 checks assessed
- AI and LLM economics70 / 100 · B
Do the AI features have a viable cost structure9 of 9 checks assessed
Open issues
Counts only. What each one is, where it is, and how to fix it are in the report, which the seller shares directly. A public page naming them would be a map for anyone else.
- 0Critical
- 9High
- 8Medium
- 0Info
History and ownership
- Commits
- 1,284
- Contributors
- 2
- busiest wrote 71%
- First commit
- 11 Apr 2023
- Latest commit
- 4 Aug 2026
Taking it over
- Readme
- Present
- Container build
- Dockerfile present
- Environment variables
- 26
- read by the code
- Methodology
- MV-2026.3
- coverage full
One honest caveat: this reflects commit 9f3c1a7d84e2 as of 6 August 2026. The code may have changed since. Ask the seller for a fresh scan if the sale is moving slowly.
No account needed. Verification checks this document against the signature Struck Code issued it with. It contains no source details, file names, dependency names, or repository URL, and grants no repository access. The findings behind these counts are in the seller's report, which they share directly.