Get an audit

Free, founder-run, about three a week. Public repos are easiest. Private works too — you don’t have to give repo access.

The audit is free for now — it is not charity, and I would rather tell you the trade than let you assume there isn’t one. Calibration data is required for a free audit. Permission to publish is never required. Those are two separate affirmations below.

Upper Crust subscribers on Substack get a guaranteed Bake Off / project audit. That paid tier is how the account settles without calibration data — say you’re Upper Crust in the email if you are.

Delivery today is email. A Worker that files submissions automatically is not built yet — your answers open a draft to james@usparkpass.com.

Repo URL — or write “I’ll send it privately”

What your agent built it with

Live URL, if there is one

Optional. Leave blank if there isn’t one yet.

What do you think has gone wrong?

Sealed before anything is graded. This is the positive expectation.

What’s normal churn that isn’t a problem?

The negative expectation. A seal that can only pass is not a test.

Named or anonymous in any write-up

This is preference for write-ups. Publication itself is a separate, optional consent.

Opens your mail app with the answers filled in. Nothing is uploaded from this page.

Private repo — send history, not access

You do not have to grant access. Two read-only git log commands produce two text files. Full instructions live in the Bake Off export note; the commands are:

git log --no-merges --format=%H --grep="This reverts commit" --fixed-strings > reverts.txt

git log --no-merges --pretty=format:$'\x1e%H\x1f%ct\x1f%an\x1f%s' --numstat > commits.txt

Attach those when you send the draft, or say you’ll send them privately in the repo field. Questions before you run anything: james@usparkpass.com.