Targetread

Code diligence for the buyer of a small software business

The target's code, counted before you pay

Paste the target's public GitHub address. GitHub reports its languages in bytes; this page turns the bytes into lines, marks in red pencil which line lengths are ASSUMED, and names the band that sets the price. Nothing is stored.

Public repositories only; a private one is read after payment. To see a readout now, .

W/P TR-1

Readout

Repository
none read yet
Prepared by
GitHub's REST API, read live
Reviewed by
[[NAMED REVIEWER NEEDED]]
  1. GET /repos/{owner}/{repo}not yet asked
  2. GET /repos/{owner}/{repo}/languagesnot yet asked
  3. GET /repos/{owner}/{repo}/git/trees/{branch}not yet asked

Three calls go to GitHub for each readout. Nothing is stored.

Languages, by GitHub's bytes, turned into lines
MarkLanguageBytesBytes per lineLines
No repository read yet.
Estimated lines–
  • Counted, from the source the column names
  • ASSUMED: a line length with no published measurement
  • Looked for, not found
  • Not read: a step not performed

Notes to the working paper

What a buyer asks before paying

What does the free readout count?

What GitHub publishes about any public repository: the bytes of each language, the default branch and its last push, the licence GitHub detects, the open issue count, and the files at the top level, where lockfiles and test folders show. The page divides each language's bytes by an average line length for that language, which estimates physical lines, blank and comment lines included.

17 of those line lengths were measured on named public repositories. The other 21 are ASSUMED, and printed in red pencil beside the estimate they move. The method lists every rate and the five repositories the estimate is checked against.

What does the memo cost, and when does it arrive?

$1,900 for one repository up to 200,000 lines; $3,900 up to a million. Paid at Stripe before the work starts. The memo arrives in HTML and PDF five business days after the desk has access, either as a read-only collaborator on GitHub or as a zip uploaded after payment.

The order form asks for your deadline, and it refuses payment when five business days from today would land after it.

What is in the memo, and what is not?

Counted sections first: files and lines by language, dependencies with an end-of-life table, the licence inventory, secret-pattern hits, test files, open advisories by ID, and the ShipSafe grade line. Then six sections the reviewer grades, architecture through bus factor, each grade with an evidence pointer beside it. Then refit's remediation bands, and a section listing what was not read.

No financials, no legal opinion and no valuation, on any order. A check that was not run is printed as a gap, never as a pass.

Who reads the code?

A person, on the desk's own machine, with three engines: assay, which writes each counted section as a finding that must cite its file; shipsafe, whose grade line is quoted as it prints; and refit, which prices the remediation in bands. The reviewer signs as [[NAMED REVIEWER NEEDED]].

Zero orders have been fulfilled by this desk so far. The engines have read other repositories, the fleet's own among them, and never yet a target under a letter of intent.

What if the repository cannot be read?

The whole price comes back if the desk cannot read the repository within 48 hours of payment, or if the band was wrong on our side. Refunds are issued by a person through Stripe; write to [[CONTACT EMAIL NEEDED]].

Why a fixed price?

Consultancies quote code diligence after a call, from 8,000 to 12,000 euros for an app under 100,000 lines. A buyer inside a two-to-four-week exclusivity window needs the number before the call, so this desk prices the code by its size and prints the price here.

W/P TR-3

Memo index

The sections every memo carries, in order. The sample memo fills the counted ones with this site's own repository.

Counted, each figure with its file

  1. A1 Files and lines by language
  2. A2 Dependencies, with the end-of-life table
  3. A3 Licence inventory
  4. A4 Secret-pattern hits
  5. A5 Test files found
  6. A6 Open advisories, by ID
  7. A7 The ShipSafe grade line

Graded by the reviewer, evidence pointer beside each grade

  1. B1 Architecture
  2. B2 Maintainability
  3. B3 Delivery risk
  4. B4 Security
  5. B5 Data handling
  6. B6 Bus factor

Remediation bands, then what was not read

  1. C1 Remediate, partial rebuild, full rebuild: each a cost band from refit, traced to the files it came from.
  2. D1 What was not read, as its own section of the signed memo