Skip to main content

Proofpack opens soon. Accounts and payments are not live yet. The sample report shows what you get.

New37 checks built for AI-coded apps

Sell your SaaS
with proof.

Scan your repo. Fix what buyers will ask about. Share a verified technical report that closes the diligence gap.

  • Read-only GitHub access
  • No code stored
  • See who opened your report
proofpack-demo/tasks-saas · main · d3e
57OF 100
Needs work

Capped at 69: 3 critical findings still count.

  • Security0 of 100
  • Dependencies94 of 100
  • Code health66 of 100
  • Docs52 of 100
  • Operability86 of 100
  • Ownership80 of 100
From the public demo repo. Your score comes from your repo.
checks a buyer will ask about
37
scored categories, 0 to 100
6
commit per report, SHA-256 hashed
1
lines of your code stored
0

Share the report in a listing onFlippaAcquire.comMicronsSideProjectorsor anywhere else. Proofpack is not affiliated with these marketplaces.

How it works

From repo to buyer-ready in an afternoon.

Three steps. Nothing to install on your servers, and your code is never stored.

  1. 01

    Connect, read-only

    Install the GitHub App on the repos you choose. Proofpack reads files. It never changes your code and never runs it.

  2. 02

    Scan and fix

    37 checks give a score out of 100 and a fix list. Each finding shows the file, why a buyer cares and the steps to fix it.

  3. 03

    Share proof

    Send buyers a verified report link, tied to one commit, with a content hash. You see who opened it.

The score

One number a buyer understands.

Six categories, weighted into a score out of 100. Security counts most. An open critical finding caps the score at 69, so a repo with a leaked key can never look buyer-ready.

  • High risk0–49

    Problems a buyer may walk away over.

  • Needs work50–69

    Real gaps. Fix the critical findings first.

  • Minor fixes70–84

    Sound, with a short list of fixes.

  • Buyer-ready85–100

    Ready to show. Share the verified report.

Due diligence, answered

What will a buyer ask?

Five questions come up in almost every technical due diligence. Proofpack answers each one with checks and file paths.

  • Are there secrets in the code?

    Hard-coded keys, committed .env files, secret keys in client code.

  • Can one customer read another customer's data?

    Supabase tables without row-level security, API routes without auth.

  • Can I run this myself after the sale?

    README, setup commands, .env.example, migrations, deploy config.

  • Do I get clean rights to the code?

    Copyleft licences, paid boilerplate, missing LICENSE, AI-tool markers.

  • Will it break when I change it?

    Tests, CI, TypeScript strict mode, lockfiles, known vulnerabilities.

The full report

Everything a buyer asks for, in one link.

The paid report adds an AI-written summary, the architecture, a handover plan and a data room, all built from the code of one commit. This is the demo repo's report.

  • Architecture

    An overview, a diagram and the data flow, written from the code. Every claim names a file.

    UserNext.js pagesPOST /api/tasksStripe CheckoutSupabase PostgresOpenAIStripe webhook
  • Data room

    Eight drafts you edit, then publish with the report.

    • Overview
    • Architecture
    • Setup
    • Services & costs
    • Environment variables
    • Dependencies & licences
    • + 2 more
  • Dependencies

    Every direct dependency with its licence and known vulnerabilities.

    Direct dependencies of the demo app
    PackageKnown issues
    next 14.2.337Critical
    lodash 4.17.156High
    stripe 15.8.0None
    @supabase/supabase-js 2.43.4None
  • Handover plan

    Setup steps, environment variables, services and costs, and a runbook for the new owner.

    • SupabaseFree tier, then monthly
    • OpenAIPer token, grows with use
    • StripeFee per payment

    5 setup steps4 environment variables4-point runbook

For buyers

Evidence you can check, not claims you have to trust.

A Proofpack report is tied to one commit and carries a content hash, so you know exactly what was checked. Every finding names the file. Seller notes are marked as seller notes. Use it to ask better questions faster, not as a replacement for your own review.

Read a sample report

What the buyer sees

Repository
proofpack-demo/tasks-saas
Commit
0000d3e
Version
v1
Content hash
SHA-256 of the published snapshot, shown on every page
Viewed by
Logged per viewer, per link

Pricing

Pay once per repo. Or keep every repo ready.

  • Free

    $0

    No card needed

    • Connect as many repos as you like
    • 3 readiness scans a day
    • All rule findings with fix steps
    • An AI fix prompt for each finding
  • Best for a sale

    Proofpack

    $49List price $99

    One time, per repo. $49 for the first 50 customers

    • 3 full AI reports for the repo within 30 days
    • Summary, top risks and buyer questions
    • Architecture, handover plan and data room
    • A verified share link for 90 days
    • Print or save as PDF
  • Pro

    $29

    A month, or $290 a year

    • 10 full reports a month, on up to 5 repos (fair use)
    • Share links that do not expire
    • View analytics for each link
    • Your logo on share pages

FAQ

Questions

More about data handling on the security page.

No. Proofpack reads the repo archive in memory. It keeps findings, masked snippets of 5 lines or fewer, and the report. Full files are never stored.

Walk into diligence ready.

Your first scan is free. See your score in minutes.