What is README Clew 2?

A tool that checks whether a GitHub README matches its code. Paste a public JavaScript or TypeScript repo, press SCAN, and you get a claim ledger showing every checkable README line, what the code says about it and who decided.

How does Jev take part?

Jev labels README lines with calibrated confidence, while rules and five deterministic verifiers decide what is true and Haiku explains the findings, per the project description. The digest excerpt does not show the Jev prompts.

What does the claim ledger show?

Every checkable line of the README sorted into buckets, such as Contradicted, where the README says something the code disagrees with, and Missing, where the code does something the README never mentions.

What repositories can it check?

Any public JavaScript or TypeScript repository: paste it into the web page or use the Chrome extension, then press SCAN. The project is live at readme-clew-2.vercel.app.

What outputs does it provide?

Line-linked receipts that tie findings back to code, a status badge, and JSON export, in addition to the on-screen claim ledger.

Where does the name come from?

A clew, said like clue, is a ball of thread: in the Greek myth Ariadne gave Theseus one to follow back out of the Labyrinth, and it is where the word clue comes from. README Clew follows the thread from each README line back to the code.

What is its status and license?

Apache-2.0 per GitHub metadata, created 2026-10-08 and last pushed 2026-10-11, with 3 stars and no forks. It was built for the AdaL 'What Would Jev Do?' hackathon, October 6 to 11, 2026.

Jev directory

CommunityJev Tools & CLIs

README Clew 2

A Chrome extension and web page that checks whether a public JavaScript or TypeScript repo's README matches its code: rules and five deterministic verifiers decide what is true, Jev labels README lines with calibrated confidence, and Haiku explains the findings.

See highlights Open github.com

Stars: 3
Language: JavaScript
License: APACHE-2.0
Reading time: 2 min
Published by: Community
Author: earlgreyhot1701D
Last verified: Oct 2026

earlgreyhot1701d/readme-clew-2

User repository on GitHub

View on GitHub

Checks whether your README matches your code. Chrome extension + web page for any public JS/TS repo. Rules and five deterministic verifiers decide what's true, Jev labels README lines with calibrated confidence, Haiku explains the findings. Line-linked receipts, status badge, JSON export. Built with AdaL for What Would Jev Do?

Forks: 0
Last pushed: Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.Homepage

Tagscommunity github javascript documentation verification

Works forJev for Verification Jev for Classification Jev for Code

Used inJev for Software & DevTools

Languages: JavaScript
Platforms: Chrome extension Browser Vercel AI Gateway
Capabilities: Open source

Highlights

Paste a public JavaScript or TypeScript repo, press SCAN, and get a claim ledger for every checkable README line.
Rules and five deterministic verifiers decide what is true; Jev labels README lines with calibrated confidence and Haiku explains findings.
Results sort into buckets such as Contradicted, where the README says something the code disagrees with, and Missing.
Ships line-linked receipts, a status badge and JSON export; live at readme-clew-2.vercel.app.
Built for the AdaL 'What Would Jev Do?' hackathon, October 6 to 11, 2026; Apache-2.0, created 2026-10-08.

Watch out

README and GitHub metadata reviewed 2026-10-17; the excerpt truncates inside the Missing bucket example, so the full bucket list, the five verifiers and the Jev prompt details are not evidenced. It is a hackathon build, last pushed 2026-10-11.

Questions about this entry

Short answers drawn from the linked project or page.

Reactions & coverage

Posts, threads, and videos about this entry from around the web.

Reddit: Localization QA with a decision model: meaning, terminology, and placeholders as separate checks.

Hacker News: Pick Verify: a single decision at the warehouse pick station catches confusable picks.

Show HN: Verifying robot picks with a decision modelRead the thread on Hacker News

From the Jev guides

Original write-ups on what this entry is for.

Jev at home: voice pipelines, Assist routing, and sentinels

Oct 16, 2026

How Home Assistant conversation agents, macOS voice pipelines, and an advisory sentinel put a fast typed decision in the loop — one call per utterance, thresholds in code, and a daily token budget.

Jev Tools & CLIs#home-assistant#voice#automation

Read article

Search visibility, audited by decisions

Oct 16, 2026

Jev-based SEO tools split the crawl from the call: deterministic crawlers count and parse, while typed judgments rank fixes, place internal links, score search results, and track AI-answer mentions — with costs and caveats attached.

Jev Tools & CLIs#seo#search-visibility#audits

Read article

Jev on the Gateways: Vercel, Workers AI, and OpenRouter

Oct 12, 2026

The request shape barely changes across surfaces; the surrounding contract does. When to call the API directly and when a gateway, a Worker binding, or a router entry earns its extra hop.

Jev Tools & CLIs#gateway#vercel#cloudflare

Read article

From the Jev AI model community

Posts from builders shipping with Jev right now.

Follow @typesafeai

README Clew 2

Highlights

Questions about this entry

What is README Clew 2?

How does Jev take part?

What does the claim ledger show?

What repositories can it check?

What outputs does it provide?

Where does the name come from?

What is its status and license?

Reactions & coverage

More Jev resources like this

From the Jev guides

From the Jev AI model community