Technical due diligence for SaaS sales
Prove your code is worth buying, without handing it to everyone who asks.
Buyers want to see the code before they pay. You do not want to give it to every tyre-kicker, and refusing looks like a red flag. Struck Code reads your repository once, grades it, and gives buyers a third-party answer they can check themselves.
- Read-only, one repository
- Source never kept
- No training on your code
Certificate of code assessment
Methodology MV-2026.3 · Issued 6 August 2026
Issued in respect of
Loopnote · customer feedback widget for SaaS
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.
34,212 lines · TypeScript 71% · 6 deployable services · 2 contributors · 3 years of history
Reflects commit 9f3c1a7
as of 6 August 2026
- Claims and functionality54 · C-
- Security70 · B
- Billing integrity80 · A-
- Code quality and maintainability73 · B
- Tests and CI55 · C
- Dependencies, licensing and IP80 · A-
- Operability and transferability65 · B-
- Provenance and bus factor85 · A
- AI and LLM economics70 · B
struckcode.com/verify/
VC-01J9XKQ2
0 critical · 9 high · 8 medium open
3 of 7 claims verified in code
Struck Code attests that the codebase identified by the hashes below was analysed in full at the stated commit, under methodology MV-2026.3.
VC<01J9XKQ2<<STRUCK<CODE<<LOOPNOTE<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
9F3C1A7D84E2<B67<<20260806<MV20263<<B41E77C0D9A5<<<<<<<<<<<<<<<<
Struck code certificate· Loopnote
VC-01J9XKQ2 · commit 9f3c1a · 6 Aug 2026
0 critical · 9 high · 8 medium · 3 of 7 claims verified
The certificate a buyer sees on your listing. Public, checkable, bound to one commit.The badge a buyer sees on your listing. Public and checkable.
- Selling now
You are listed, or listing this month
Get the graded certificate a buyer can check without you handing the repository to anyone.
You are here - Selling later
You will sell, but not yet
Find out what a buyer will find while there is still time to fix it. A grade now is a to-do list.
Read this instead - Buying
You are looking at someone else's listing
The seller will not show you the code. Ask them for a certificate instead. It is free to start.
Read this instead
Three things, from one read of your repository
The full report
Every finding with its location, evidence, buyer impact, and fix. Yours to share or keep.
A public certificate
A graded scorecard bound to one commit, at a link anyone can check. No repository access needed.
A free preview
About 30% of the findings, shown before you pay. You judge the depth before spending anything.
Nine dimensions, weighted the way a buyer cares
Every grade is the same arithmetic on the same checks. The weights are public, so a buyer knows exactly what a B- means before they ask you a single question.
Read the methodology, MV-2026.3- Claims and functionality25%
- Security20%
- Billing integrity10%
- Code quality and maintainability10%
- Tests and CI10%
- Dependencies, licensing and IP10%
- Operability and transferability10%
- Provenance and bus factor5%
- AI and LLM economics8%
Nobody should buy this without seeing a report first. Here is one.
A worked example, scored by the same engine yours will be, with the preview wall exactly where yours would be. Five minutes of reading tells you whether this is worth $299.
See the sample reportRead-only, one repository
We cannot write to it, and we never see your others.
Single-use machine
Analysis runs on one commit inside a machine that is destroyed afterwards.
Source never kept
Findings, short excerpts, and hashes are all that survive.
No training, ever
Your code never trains a model. Ours or anyone else's.
One price. No tiers, no subscription.
The full report, the public certificate, and one fix-and-rescan so acting on the findings is free. The certificate is issued whatever the grade turns out to be.