readme · clew
AUDIT YOUR OWN RECEIPTS
Does your README tell the truth? Paste a public GitHub URL — Clew extracts every factual claim and checks it against your actual code. Findings only. No rewrites. Nothing saved.
what a scan looks like
the readme claims "uses Express for HTTP routing"
the code confirms: express found in package.json
the readme claims "85% test coverage"
the code cannot confirm — requires running tests to verify
the readme mentions nothing about SESSION_SECRET
the code does not show: process.env.SESSION_SECRET used in source but absent from readme
the readme claims "install with npm install"
the code contradicts: yarn.lock present — no package-lock.json found
❦
❦ WHAT WE CHECK
declared dependencies — readme says you use a package, we check package.json
install and run commands — readme documents a script, we check it exists
environment variables — readme mentions an env var, we check your code reads it
file and url references — readme points to a path or link, we check it resolves
code-vs-package coverage — imports in code cross-referenced with declared deps
⁂ WHAT WE DON'T
private repos — public only in v1
runtime claims — "85 tests passing" requires running tests
subjective claims — "blazingly fast" is not checkable
non-JS repos — JavaScript and TypeScript only in v1
writing quality — that's your business
readme · clew
fetching readme...
extracting claims and verifying against code
dependencies
commands
envvars
references
coverage