How to batch report in developer workflows
- Step 1Use it during code review — When reviewing a PR that ships an archive artifact, drop it into the Batch Report to report compression stats across many archives without checking out the branch. Quicker than rebuilding locally.
- Step 2Pair with the Archive Diff — For PRs that change archive contents, run /archive-tools/archive-diff over the before/after to see exactly which entries changed — equivalent to diff -r on extracted trees.
- Step 3Build a reproducible pipeline — Combine Batch Report → Timestamp Normaliser → Checksum Generator. The output is a bit-identical archive across machines, with a SHA-256 manifest your CI/CD can verify.
Frequently asked questions
Is there a CLI or API equivalent?+
Programmatic access is planned for Phase 15. Today, the closest equivalents are: fflate (Node) for ZIP/GZIP, libarchive bindings for 7Z/RAR, and the Web Crypto API for SHA-256 manifests. JAD wraps all three behind one UI.
How do I make the output reproducible?+
Run the tool, then pass the result through the Timestamp Normaliser with a fixed date (1980-01-01 is the standard for reproducible builds). The Per-File Checksum Generator emits a manifest your CI/CD can verify against future builds.
Can I script bulk batch report runs?+
Free tier: one file at a time. Pro: up to 20 files per batch. For larger volumes use the Batch Extraction Manager (extraction tools) or Batch Compression Report (analysis tools) which accept many archives at once.
Does the output work with my CI/CD format expectations?+
The output is a standard archive readable by any consumer. There's no JAD-specific format or wrapper — drop it into your existing CI step.
Privacy first
Every JAD Archive tool runs entirely in your browser using fflate, @zip.js/zip.js, and the libarchive WASM bridge. Your archives never leave your device — verified by zero outbound network requests during processing.