Third-party source code: PubVia
PubVia is an Eclose product. It includes software written by others. Three of them are under a copyleft licence, the GNU LGPL: libheif and its libde265 decoder (version 3 or later), and libheif-js (version 3.0), which builds the two into a WebAssembly bundle. All three are built into docx, the program PubVia uses to read and write Word files. The LGPL requires us to offer their corresponding source code and to let you rebuild docx with your own modified copy of any of them. This page explains how to do both; the steps below cover libheif.
PubVia itself is proprietary. This page covers only the third-party software it includes and the patches we made to that software.
Download the source
The source of each published PubVia release is on pubvia.eclose.bio:
- Index of releases. Each row is one PubVia version, with the date its source was published, the SHA-256 checksum of its
docxand a link to the index of that release. - Each release index has one row per file, with its version, its licence, its original download address and its SHA-256 checksum. The files are at
https://pubvia.eclose.bio/sources/followed by the PubVia version and the file name.
Each release folder contains:
- the source of libheif, libde265 and libheif-js (libheif and libde265 compiled to WebAssembly with Emscripten), plus the build scripts of libheif-emscripten, which produce libheif-js;
- the source of docx-cli (MIT licence, by Kirill Klimuk), which
docxis built on, and our patches to it, released under the MIT licence, Copyright (c) 2026 Eclose; BUILD.txt, with every step needed to rebuilddocx.
Each file is the upstream source of the exact version we ship: a release tarball, the npm package, or an archive of the exact commit. Each release index gives the upstream address of every file, so you can check it against the artifact it came from. Starting with PubVia 0.1.49, we publish the source folder of a release before anyone can download the release. Once published, a folder is never changed or deleted.
Rebuild docx with your own libheif
docx is docx-cli with our patches, compiled into a single executable as described in the BUILD.txt of your release, which has the exact commands and versions. To use your own libheif:
- Compile it to WebAssembly the same way libheif-emscripten does, with the Emscripten version and options listed in
BUILD.txt. - Regenerate
libheif-wasm/libheif-bundle.jsfrom the libheif-js source.docxloads libheif only from this file, so replacinglibheif.wasmon its own has no effect. - In the patched docx-cli, after
bun install, copy the result intonode_modules/libheif-js/libheif-wasm/, then run only the build line. Runningbun installagain would overwrite that folder. - Quit PubVia, replace
docxinside the app with your build, and sign the app again with an ad hoc signature.
Other included software
The full list of included components, with their versions and licences, is in the THIRD_PARTY_NOTICES file inside the app. In PubVia, open Settings, then About, then “Open-source licenses”. Apart from libheif, libde265 and libheif-js, no component is under the GNU GPL or LGPL. The other components include:
- Citation styles and locales from the Citation Style Language project. These are data, not software, under CC BY-SA 3.0, a share-alike licence.
- Geist and IBM Plex Mono fonts. SIL Open Font License 1.1.
- PDFium, inside
docx. BSD-3-Clause.
Request a copy
To get a copy of the corresponding source of any component above, email main@eclose.bio with your PubVia version and the name of the component. We send it free of charge, for at least three years after we last distribute that version of PubVia.
This offer covers every PubVia release in the index of releases.
Licence text
The text of the LGPL 3.0 is inside the app, next to docx, together with the docx-cli notices. It is also at gnu.org/licenses/lgpl-3.0.html.