EPUB Package Reference Reviewer

How to use EPUB Package Reference Reviewer

Find missing local package targets and inconsistent reading-order references before a broader ebook review. ZIP limits are checked before selected metadata is decompressed. Remote resources remain an explicit unverified inventory, and a clean reference report is never presented as full EPUB conformance.

1. Choose a local EPUB file or load the original generated example.
2. Run the metadata review; examine container issues, manifest states, fallback chains and ordered spine references.
3. Download the JSON evidence and use a full EPUB checker plus reading-system/accessibility testing before distribution.

Good to know

• 4 MiB ZIP, 200 safe entries, stored/DEFLATE only, no ZIP64/encryption/symlinks, and the existing 100× expansion limit. Selected metadata: 200,000 bytes per XML, 1,000,000 aggregate bytes, 6 documents, 40,000 total elements, 60 nesting levels and a checked 5-second processing budget.
• 1–4 package rootfiles; at most 200 manifest and 200 spine items per package. XML must be UTF-8 with no DOCTYPE/entity declarations. Encryption or font obfuscation metadata is refused. Local references support relative percent-decoded paths, with no query, fragment, root-absolute path, encoded separator or escape above the container root.
• Only selected metadata CRCs are checked. No chapter rendering, full XML schema/content validation, remote fetching, reading-system behavior, accessibility audit, DRM or malware determination is performed.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.