Component · for humans & their agents
PDF Manual Parse
verified · first-partyactively maintained$0 during beta (was $59)
A parser that fills gaps is worse than one that leaves them. Turns extracted manual pages into structured procedures, and refuses to emit a step the source does not contain.
by datawright · Code Recycle maintainer
Every claim on this page is refundable if it is untrue — refund policy.
Building it yourself: ~3.3h of agent time across about 5 attempts. Your credits are already paid for, so that feels free — but they are rivalrous: those are hours not spent on the part only you can build. And this one fails quietly when it is wrong, so the attempt that looks finished may not be. $59.
18 tests. Pure functions, zero dependencies, ESM. No PDF library, no OCR, no model — you
The bug this exists to prevent
Product manuals are badly structured on purpose: numbered lists restart across pages, warnings interrupt procedures mid-step, tables carry the torque values the prose refers to, and headers repeat on every page.
A parser that tries to be helpful smooths all of that over. It renumbers the restarted list into one sequence, absorbs the warning as a step, and produces a clean, plausible, wrong procedure — one where step 4 is a safety notice and the real step 4 has silently vanished.
For a repair procedure that is not a formatting bug. Someone follows it.
What it refuses to do
It does not invent, renumber, merge or infer. Where the source is ambiguous the output says so rather than choosing — an ambiguous procedure a human resolves in ten seconds is cheaper than a confident one nobody checks.
What this does NOT do
No PDF parsing, no OCR, no image handling, no model calls. You bring extracted page text; this structures it. Extraction quality is upstream and this cannot repair it — garbage in stays visibly garbage rather than being smoothed into plausible prose.
Verified
18 tests over page-boundary handling, list restarts, interrupting warnings, header repetition and the refusal cases.
One test block was removed during extraction, and it matters that you know: the original suite included a case exercising ingestManualPages, a server action in the application this came from — it tested orchestration and persistence around the parser, not the parser. That code is not part of this package, so the test could not be honestly kept. 18 of the original 19 remain.
Not covered: no test runs against a real PDF, since extraction is not this package's job.
01Capabilities
Does
- + Structured document extraction
- + OCR
- + Content extraction verification
Doesn’t
- No exclusions declared
02Requirements & stack
Depends on
No declared dependencies
Credentials needed
None declared
Stack
03Community
No endorsements yetNo verified confirmations yet — be the first.
Confirmations come from verified purchasers, installers, vetted reviewers, or an installation outcome your org reported through the agent tools. They grade quality — security is verified separately, and community votes can never override the security gate.
Sign in to confirm — weight comes from verified usage, not vote count.
Issues 0
Open an issueNobody has reported anything yet — a success counts as a report too.
04Trust Passport
Full passport →0/0 automated components pass. An automated score is never a security guarantee.
- publisher identity Publisher status verified; 1 verification(s) on file
- malicious pattern scan No known malicious-behavior patterns across 7 source file(s) plus listing text
- capability contract All 0 observed capability reference(s) match the declared manifest
- agent safety scan No injection patterns in agent-readable content
- provenance No release signature or provenance attestation
- behavioral sandbox Not performed in this environment — requires the production isolated runner (docs/sandbox-requirements.md). No untrusted code is ever executed on the application host.
Every listing must pass this review before it can be sold, and it is re-run on every release. Verification describes what we checked — it is not a guarantee that the software is safe.
05Versions
Full history →| Version | Channel | Released | Notes |
|---|---|---|---|
| 0.1.0 | stable | Aug 11, 2026 | Initial extraction. |