Registry · Paper development & review · Revise manuscripts from feedback
textlint/textlint
Live AHK-0052
Identity
- Repository
- textlint/textlint
- Repository id
- 28478929
Description
Editorial draft Pluggable text linting in TypeScript with fix and dry-run modes; recorded as machinery for controlled language passes.
The campaign that admitted it
2026-07-30__feedback-driven-manuscript-revision · · run type (the campaign's own designation) high-recall-map
High-coverage, effort-bounded, not saturated as of 2026-07-30: no single inspected public work supplies the whole feedback-to-document loop, so the strongest design is a supervised orchestrator combining multi-selector comment anchoring with orphan/ambiguity states, editorial diagnosis with global-before-local planning, and small reversible explained proposals under author decision.
Claim wording is the campaign's own, including its shorthand — see the methodology glossary.
2 ledger rows cite this repository.
The claim is the campaign's own record — its coverage and its judgments — quoted word for word. It is not this site's assessment of the repository.
Current metrics
- Stars
- 3169
- Forks
- 165
- Watchers
- 32
- Language
- TypeScript
- License
- MIT
- Archived
- No
- Created
- Last push
- Topics
- javascriptlintlintermarkdownnatural-languagenlptextlint
- Snapshot
- · retrieved UTC
Counts only. This site never publishes stargazer, watcher or contributor identities.
Weekly movement
First snapshot 2026-08-10 — weekly movement begins with the second.
Star history
Not yet backfilled. Source will read: an independently collected archive of the same platform's public events, plus our snapshots.
Trust marks
- Snapshot
- · retrieved UTC
- Entries hash (sha256, first 12)
-
46fcea8cb0e2— this hub's served data file — verifiable at /api/entries.json - Snapshot hash (sha256, first 12)
-
5029a1dd0e77— raw capture, shared by both hubs (not yet published) - Method version
- supervised beta (v3.3 taxonomy)
- Sealed record
- 2026-07-30__feedback-driven-manuscript-revision — named, not linked; the record is not public.
What we collect
Collected per entry, weekly, append-only and hash-attested — the full field list is on the data card. Aggregate public metrics only; no stargazer or contributor identities. The posted record is public and quotable; the collection run itself is not published.