LordOS — a free, fast and secure GNU/Linux distribution based on Debian, with its own desktop environment: display server and Wayland compositor in C, a React UI engine on QuickJS, and private native apps.
License compliance and the SBOM
How LordOS keeps track of what it ships and under which licenses, and the software bill of materials (SBOM) published with each release. The website summary is at lordos.org/legal/standards; the user-facing license page is lordos.org/legal/licenses.
The license inventory
LICENSE: LordOS's own code, MIT.THIRD_PARTY.md: every component bundled in the repository (third_party/), the fonts and data files inassets/, the npm packages bundled into the theme JavaScript, and the Debian libraries LordOS links dynamically, each with its license. A new bundled component, font or data file is added there in the same change that adds it.- The
.debcarries a machine-readableusr/share/doc/lordos/copyright(Debian copyright format, written bytools/iso/mkdeb.sh), and each font ships its license text next to it (assets/fonts/*-LICENSE.txt). - Debian packages keep their own
/usr/share/doc/<package>/copyrighton the installed system. - Raspberry Pi packages mirrored in the LordOS APT repository (arm64, since 0.8.4.1;
tools/release/rpi-mirror.list, UPDATES.md, "Raspberry Pi firmware packages") are copied byte for byte, each with its owncopyrightinside:rpi-eeprom(scripts BSD-3-Clause; bootloader images under Raspberry Pi's binary licence, which allows redistribution of unmodified binaries for use with Raspberry Pi devices with the notice),raspi-utilsand its parts (BSD-3-Clause) andkms++(MPL-2.0). For the MPL-2.0 binaries the corresponding source, thekms++source package of the same version from Raspberry Pi's archive, is published next to them at https://lordos.org/apt/pool/rpi/source/k/kms++/ (pinned inrpi-mirror.listwith architecturesource, verified against Raspberry Pi's signedSourcesindex, kept in the append-only pool); upstream ishttps://github.com/tomba/kmsxx. A new pinned kms++ version needs itssourceline too. - The app catalog (0.8.5, Store → Artificial Intelligence and Commercial;
apt/catalog.json,apt/README.md, UPDATES.md, "Mirrored apps (catalog)") records each app's licence. Apps delivereddirect(Claude Code, Claude Desktop, Visual Studio Code, Cursor, Google Chrome, Microsoft Edge, Spotify, all proprietary) are not redistributed by LordOS: the Store adds the vendor's own signed APT repository with a pinned key, and the package comes from there under the vendor's terms. The packages published inpool/catalog/are goose (Apache-2.0) and opencode (MIT), the vendors'.debfiles unmodified with a pinned SHA-256, and three LordOS builds:llama.cppandwhisper.cpp(MIT), built from the upstream source tarball pinned by URL and SHA-256 in the catalog, andcodex-cli(Apache-2.0), OpenAI's static binary with its sigstore signature checked.
The SBOM
tools/release/make-sbom.sh writes an SPDX 2.3 JSON
document for a built package:
| Part | What | Version from |
|---|---|---|
lordos |
the .deb itself: version, architecture, SHA-256, download URL on GitHub Releases, MIT |
dpkg-deb -f |
| Bundled code | QuickJS, Monocypher, stb_image, stb_image_write, stb_truetype, the EFF and SecLists word lists, react, react-reconciler, scheduler, the Unicode data | third_party/*/VERSION, the stb headers, package-lock.json, server/src/ui/unidata.h |
| Fonts | Inter, Plus Jakarta Sans, JetBrains Mono (OFL-1.1), with the SHA-256 of each .ttf in the package |
the font's revision (fc-scan, when fontconfig is installed) |
| Data | DB-IP Lite Country (CC-BY-4.0) and Natural Earth (public domain), with the SHA-256 of the files in the package | not versioned |
| Debian packages | every package in the .deb's Depends (DEPENDS_ON) and Recommends (OPTIONAL_DEPENDENCY_OF), with a pkg:deb/debian/… purl |
dpkg-query on the machine that runs the script |
For an alternative (libssl3t64 | libssl3) the first one installed is listed. A dependency that is
not installed on the machine is listed without a version and the script prints a warning. Debian
package licenses are NOASSERTION in the SBOM; the authoritative text is each package's
copyright file.
Generating it
On the Debian 13 build VM, after building the package and with its dependencies installed (so the versions are the ones the release was built against):
tools/release/make-sbom.sh out/lordos_0.8.0_amd64.deb # -> out/lordos_0.8.0_amd64.spdx.json
LORDOS_TAG=v0.8.0-beta tools/release/make-sbom.sh out/lordos_0.8.0_amd64.deb release/lordos_0.8.0_amd64.spdx.json
LORDOS_TAG sets the release tag used in the download URL (default v<version>). The script
needs dpkg-deb, dpkg-query and python3; fc-scan is optional.
Publishing it
Starting with v0.8.0-beta, the SBOM of each architecture is attached to the GitHub release next to
SHA256SUMS. Put it in the release folder before tools/release/sign-release.sh: that script
hashes every file in the folder, so the SBOM is listed in SHA256SUMS and covered by the release
signature (see SIGNING.md, "Release files").
Standards
Our processes are aligned with, not certified against, these standards. What is in place and what is still missing is listed on lordos.org/legal/standards:
- ISO/IEC 29147 and ISO/IEC 30111: vulnerability disclosure and handling (
SECURITY.md, the security policy and/.well-known/security.txt, RFC 9116). - ISO/IEC 5230 (OpenChain): this inventory, the license notices and the SBOM.
- ISO/IEC 18974 (OpenChain security assurance): the SBOM plus Debian's security updates for the packages we depend on.
- WCAG 2.2 AA as the website's accessibility target.
Gaps today: no formal OpenChain conformance self-certification, no automated matching of the SBOM
against vulnerability databases, no SBOM for the ISO and Raspberry Pi images as a whole (only for
the .deb and what it depends on), and no third-party audit.