Libera Suite
A desktop office suite that belongs to you. Libera Suite opens the documents other people send you (.docx, .xlsx, .pptx, ODF), edits them on your machine and saves them back. It runs on your computer, with no account to create and nothing in it that phones home.
Five editors share one application. The file picks the editor, so there is nothing to choose.
| Libera Words | .docx .odt .rtf .txt .md |
| Libera Tables | .xlsx .ods .csv |
| Libera Slides | .pptx .odp |
| Libera PDF | .pdf: comment, fill in, rearrange |
| Libera Diagrams | opens .vsdx to read |
Abilian builds the host as free software under the Apache License 2.0. The editors inside it come from Euro-Office (an AGPL fork of ONLYOFFICE by Ascensio System SIA), running locally. A short patch queue of ours makes them build on each platform, brands them, sets a few of the editor's options, and fixes bugs, most of them in the converter.
Using it
libera report.docx # a window, in Words, because the file says so
libera budget.xlsx # Tables
libera *.pptx # one window each
libera # the start window: new, open, recent
What works today sets out the full list with its gaps. It covers editing, saving and exporting, with PDF in the Save As popup. It also covers blank documents, images, printing, spell check in six languages, crash recovery and a Recent list.
libera -v FILE # what it is doing; -vv how; -vvv every request
libera --diagnose # everything worth pasting into a bug report
libera --payload-status # which editors are in use, and the revisions they were built from
How it works
The editors are a web application. Everything they cannot do in a browser (read a file from disk, convert it, save it, list the fonts, put a dialog on screen) they ask of one injected JavaScript object, window.AscDesktopEditor, which the host exists to answer.
We implement it in Python, behind the webview your system already ships. The host serves the editor over a loopback HTTP server and defines AscDesktopEditor before the editor's code runs, so nothing about the editor changes.
| The payload | The editors: sdkjs, web-apps, the x2t converter, fonts, dictionaries. Built from upstream sources pinned by SHA, plus our patch queue. Two Python packages, libera-core and libera-web, about 100 MB to download, or inside the bundle. |
| The host | src/libera/: the loopback HTTP server, the webview, the file dialogs, the menu bar and the converter calls, in about 12,000 lines of Python across 60 modules. All of the desktop application is here. |
| The bridge | Three small JavaScript files, spliced into the <head> of every page the host serves. Our code and theirs never share a file. |
We do not fork the engine. The patch queue makes upstream build on macOS and Windows, brands it, sets a few of the editor's options (no upstream helpdesk, no macros), and fixes bugs. Most of those are in the converter, for OpenDocument files. A handful are in the editors, among them font substitution and two cross-site scripting holes. Each patch is small and explained, so following upstream means rebasing a short series. Every release records the exact revisions it was built from, so the corresponding source is a commit plus a series that provably reapplies to it, and lb payload check checks that it still does.
Everything we ship, we build. build/ compiles the editors and the native converter from pinned upstream sources, on all three systems, with our patch queue applied.
Where it stands
Early, and running. All five editors work today on Windows 10 and 11 (x64), Linux (x86_64; arm64 stays on 0.4.1) and macOS (Apple Silicon).
Tabs on Linux and Windows, and signing on macOS and Windows, are still to come. Linux and Windows have a menu bar drawn in the window, which shows few keyboard shortcuts on Linux and none on Windows. What works today lists the known issues, so an evening spent reporting one is an evening wasted. The roadmap says what comes next and what we have decided against.
The most useful thing you can send us is a document that renders wrongly, attached. The layout engine is upstream's and mature, so where output is wrong it is far more likely to be our packaging (a font we did not ship, a resource we failed to serve) than the engine.
Installing it
Install gives the full instructions for each platform. There are four ways in. The first works on Linux and macOS alike.
One command, no root. It picks the channel that suits the machine:
curl -fsSL https://cdn.abilian.com/libera/install.sh | sh
Homebrew, on Linux and macOS alike:
brew install abilian/tap/libera
Linux: the Flatpak. The bundle includes the editors, GTK and WebKit, so there is nothing else to fetch and nothing to get wrong:
arch=amd64 # or arm64
ver=$(curl -fsSL https://cdn.abilian.com/libera/bundles/latest)
curl -fLO "https://cdn.abilian.com/libera/bundles/libera-$ver-$arch.flatpak"
flatpak install --user "./libera-$ver-$arch.flatpak"
flatpak run eu.liberasuite.Libera
From PyPI, where the editors are two packages of their own, libera-core and libera-web, which libera requires:
pipx install --system-site-packages libera # Linux: the flag is not optional
uv tool install libera # macOS
Linux is x86_64; arm64 stays on 0.4.1 for now. The converter is built on Ubuntu 22.04 and needs glibc 2.34 and GLIBCXX 3.4.29: Ubuntu 22.04, Debian 12, Fedora 36, RHEL 9 and anything newer, measured in a clean container of each. The Flatpak needs none of that, since the editors inside it run against the GNOME runtime.
macOS is Apple Silicon, on macOS 14 or later. There is no Intel build.
Building it
git clone https://github.com/abilian/libera-suite && cd libera-suite
uv sync
make payload # fetch, patch, build, assemble, smoke-test (long: V8 alone is ~30 min)
export LIBERA_PAYLOAD="$BUILD_ROOT/out/payload"
uv run libera document.docx
make verify # everything below, in the order that fails fastest
make test # unit, the host over HTTP, the editor in headless Chromium
make lint # ruff, ty, pyrefly, mypy, biome — green, and expected to stay that way
lb payload test # the converter: fonts, docx -> odt -> docx, docx -> pdf
lb payload check # does the patch queue still apply to the pinned SHAs?
The test suite enforces one house rule: assert on content, never on exit codes. A converter that writes an empty document exits zero. A PDF with no glyphs in it is the right size. So the end-to-end run photographs the editor's canvas and measures the ink on it.
docs/ |
The documentation site, published at https://docs.liberasuite.eu/. Start at Developers. |
notes/ |
Where the reasoning lives: vision, specs, architecture, packaging, our relationship with upstream, the bugs that escaped to a user, a survey of how Euro-Office is put together. It stays in the development repository. |
build/ |
Building the editors and the native binaries from pinned source plus our patches. |
The package and the command are libera. The repository directory is local-office.
Credit
Libera Suite includes components from Euro-Office, itself a fork of ONLYOFFICE by Ascensio System SIA. Those components are AGPL v3 and are modified. The same line appears in Help ▸ About inside the application, in the editor's About panel, and in what a software centre shows for the Flatpak.
The editors, the document engine and the format support are theirs. That is the hard part: twenty years of correctly reading a .docx written by somebody else's software. The host, the packaging and the desktop integration are ours. We are grateful for both.
Licence
Libera Suite ships as two artifacts under different licences.
The host is Apache-2.0: everything in src/libera/, which is the whole of this package.
The editor payload is AGPL-3.0: Euro-Office plus our patch queue against it (GUI assets are CC-BY-SA-4.0). It arrives as two separate packages, libera-core and libera-web, or inside a bundle, never vendored into the host's wheel.
Licence and attribution has the corresponding-source detail: what each release records, and where to fetch it.
Metadata
Release files for libera 0.7.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| libera-0.7.2.tar.gz | 356.3 kB | Without provenance | Details for libera-0.7.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| libera-0.7.2-py3-none-any.whl | Python 3 | none | any | Details for libera-0.7.2-py3-none-any.whl |
Total release size: 826.9 kB
Release files / libera-0.7.2.tar.gz
| Download URL | libera-0.7.2.tar.gz |
|---|---|
| Size | 356.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6b021b9c0f587f262d5b9b3391211e94f893c8a7b7e0154c0dc7b9963e6de46f
|
|
BLAKE2b-256 checksum How to use checksums |
8d388d344581510d2287ced798f11ee278a8846a155b657f7d25f4f536fbe016
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / libera-0.7.2-py3-none-any.whl
| Download URL | libera-0.7.2-py3-none-any.whl |
|---|---|
| Size | 470.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71ff2f00e024e0d0e53dc964bb6390abf3edb7b0bacbb3f5046f69c347a673a9
|
|
BLAKE2b-256 checksum How to use checksums |
fb5c131e69fcc30d4ee143b192eaeae09a6fc93f9a75ea2a660a9c355eb763fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.4 {"installer":{"name":"uv","version":"0.13.4","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for libera 0.7.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.