Registry · Tools & document processing · Parse PDFs & documents
run-llama/liteparse
Live FHK-0077
Identity
- Repository
- run-llama/liteparse
- Repository id
- 1153982569
Also filed on the survey's other hub.
Description
Editorial draft A small Apache-2.0 geometry and OCR baseline in Rust; its own documentation bounds it away from dense multicolumn work.
The campaign that admitted it
2026-07-28__pdf-parsers ·
run type (the campaign's own designation) high-recall-map
A high-coverage, effort-bounded map as of 2026-07-28 ranking five Apple-plausible local parsers (Marker v2 first, medium confidence); the coverage gate is NOT MET, no global winner or recall proof is asserted, no candidate was installed or executed, and multilingual support earned zero credit.
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. Claim wording is the campaign's own, including its shorthand — see the methodology glossary.
2 ledger rows cite this repository.
Current metrics
- Stars
- 11993
- Forks
- 823
- Watchers
- 36
- Language
- Rust
- License
- Apache-2.0
- Archived
- No
- Created
- Last push
- Topics
- document-ocrdocument-processingocrocr-recognitionpdfpdf-parsertext-extraction
- 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)
-
40e9e9c1efa4— 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-28__pdf-parsers — 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.