The image and the gate as in 47138dd: the zero-host gate green on all 117
enabled tool pages (CI form, private network, 3 min 52 s), red on the stock
image (115 findings) and on a misspelled disabled id.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.9 KiB
1.9 KiB
Changelog
All notable changes to this project are documented in this file. The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[Unreleased]
[0.1.0] - 2026-10-10
The first release: BentoPDF v2.8.8 for bau-pm, about 120 PDF tools that run in the browser and talk to no third party, with the hand-off that brings a PDF from bau-pm into a tool and the result back.
Added
- BentoPDF v2.8.8 built from source at its pinned commit with BentoPDF's air-gapped build options: Simple Mode, German by default, every module served from the image's own
/wasm/, the CORS proxy off. - The CDN modules vendored and checked against
vendor.lock(PyMuPDF, Ghostscript, CoherentPDF, Tesseract with German, French, Italian and English, the OCR font, the PDF editor's Latin, Arabic and Hebrew fallback fonts). Ghostscript is served as its whole package withgs.jsandgs.wasmlinked at its root, because BentoPDF's own loader and PyMuPDF's wrapper expect the two different layouts (upstream's air-gap layout leftpdf-to-docxwith a 404). - A Content-Security-Policy without any host,
img-srcincluded; the build fails if one survives. digital-sign-pdfandtimestamp-pdfdisabled: both need a third party by design.- The hand-off glue on every page: a source link (AGPL), the hand-in of a file from bau-pm through a one-minute cookie into the tab's
sessionStorage, confirmed by the tool's own reaction and retried while it has none (BentoPDF attaches its listener late, and its service worker made the glue win that race), the hand-back of a result caught in every window, the viewer's frame included, and waiting for the hand-off's details when a save comes before them, and the signing tool's flatten switch locked on. - The zero-host gate (
test/zero-hosts.mjs) over every tool page, in CI and in the release workflow.