Licences

Open-source licences

NoblePDF self-hosts and pins the open-source components used across its public tools and its separate PDF editor application. This inventory distinguishes which runtime families are deployed on each origin.

Open-source software used by NoblePDF

NoblePDF uses two deployment origins: noblepdf.com for public tools and editorial content, and app.noblepdf.com for the persistent PDF editor. Dependencies are packaged only where they are needed. The engineering release includes THIRD-PARTY-NOTICES.md, the vendor manifest and upstream licence material where required. This page is a product-level attribution inventory; it does not mean every component below is shipped on both origins, and it does not replace the original licence texts.

Runtime component inventory by deployment origin

Public site and standalone tools - noblepdf.com

PDF editor application - app.noblepdf.com

The engineering package contains the authoritative vendor manifests, hashes and upstream licence notices for both deployment origins. The public deployment does not carry editor-only Fabric.js. qpdf-wasm is intentionally present on the public origin because the Preserve text & vectors compression mode executes qpdf locally in the browser.

Why versions matter

Document libraries can change behaviour between releases. NoblePDF pins runtime files and checks their SHA-256 values before packaging so a production release does not silently use different third-party bytes from the engineering build. Security and licence audits should therefore review both the named component and the exact shipped version.

Questions about a component

If you believe an attribution is missing or incorrect, contact contact@noblepdf.com with the component name and the relevant upstream licence information.