PDF navigation field notes / v0.1
Find the links your PDF converter quietly broke.
One local command inventories every link annotation, checks where it lands, and leaves a clickable map for reviewers and CI.
Local by design. Your PDF never leaves your machine. External addresses are listed, never opened.
Internal named + explicit destinations
External recorded, never fetched
Output HTML + JSON + exit codes
Method 01
Make navigation a release artifact
Run the same audit after LibreOffice, Chromium, wkhtmltopdf, or any other converter. The checker reads the finished PDF—not the tool that made it.
- 1
Inspect annotations
Inventory GoTo and URI actions without rendering pages or contacting the network.
- 2
Resolve destinations
Follow explicit pages and PDF name trees. Flag missing pages, anchors, and duplicates.
- 3
Leave evidence
Open the standalone HTML map for review, or consume JSON and stable exit codes in CI.
Field command
A single binary. No account.
Build from source today. Release binaries can be attached without changing the command or report schema.
cargo install --git https://github.com/B-Divyesh/sf-pdf-link-map
pdf-link-map handbook.pdf \
--manifest headings.json \
--fail-on broken --json
Pinned specimen
Read a link map before you make one
This browser specimen uses bundled, non-sensitive sample results. Actual PDFs are inspected only by the local CLI.
2 routes need attention
| From | Destination | Result |
|---|
Team notebook
Keep the checker free. Unlock the rollout kit.
The free CLI always includes complete audits, HTML and JSON export, manifests, and failure thresholds. A one-time Team unlock adds a guided CI policy builder and maintained release-pipeline recipes for documentation teams.
Sociobot/Dodo is the merchant of record. Refunds are handled there and revoke the license automatically. Privacy · Terms
Unlocked field sheet
Build your CI checkpoint
Choose your inputs, then generate a recipe.
A visible contents page is not proof of working navigation.