ObliviOS Developer portal Project site

Home / Decisions / ADR-244

Close the SBOM and claim-review gates of the source-only stage.

Accepted, recorded 16 November 2026.

Decision
ADR-244
Date
2026-11-16
Status
AcceptedAccepted (owner, 2026-11-16: the SBOM, the claim review, the branches stay private, the old commits stay). Done: the SBOM built from the commits oblivios-manifest 3ac7493, oblivios-platform 694b57b, oblivios-services 1ec3f74 and the snapshot of oblivios-docs: 858 components, 1493 files, 8 advisories, both documents schema-valid, a mutation run (a changed licence, checksum and yanked flag) failed as it must. The fixes are committed locally; oblivios-manifest, oblivios-platform and oblivios-services are not pushed yet. Coverage of the claim review: the root README, NOTICE and SECURITY.md of each repository, the source records and READMEs named in the consequences, the README and NOTICE of exit-daemon, and every number or table row that the build can compare; the prose of the other package READMEs and SOURCE.md records (about 45 files in oblivios-platform) was not read sentence by sentence, so the ADR-171 gate "every sentence of the READMEs and the NOTICE files" is met for the root files and not yet for those. Not done: the owner's read of the final set, the trademark registers, the assessment of five advisories, the aggregated licence text of the Rust packages, the record of the accepted legal risk per item (ADR-171), the change of visibility.
Mentions
ADR-171, ADR-241, ADR-243
Mentioned by
ADR-171, ADR-245, ADR-265

1Decision

Close the SBOM and claim-review gates of the source-only stage (ADR-171, ADR-241), as the owner asked on 2026-11-16 (an SBOM as strong as possible).

(1) SBOM: tools/sbom/build-sbom.py builds a CycloneDX 1.6 and an SPDX 2.3 document, a SHA-256 list of every file of the four published repositories (files.sha256) and the checks below; the build is offline and deterministic (the same commits and evidence give the same bytes) and fails when a fact is not supported: every file has exactly one rule (own work, patch, data file, prebuilt binary, manifest copy) and no file of a foreign copyright or licence sits in an own-work rule; every prebuilt binary equals the hash of its record and its source commit is on a published branch; the registry licence, checksum and yanked flag of every locked Rust package equal Cargo.lock and the records of the project (exit-daemon/NOTICE, the table of vault-core/SOURCE.md), and every licence can be met with the allowed terms; the numbers and rows of the NOTICE files and READMEs equal what the files give.

Both documents validate against the official JSON schemas. The documents, the evidence (crates.io, OSV, the licence files and file headers of the 18 patched upstream projects, Maven Central) and the scripts are published in oblivios-docs (sbom/, tools/sbom/). (2) Claim review of the READMEs, NOTICE files, SECURITY.md and source records of the four repositories; the fixes are in the consequences.

(3) The branches fix/passwords-locked-device-biometrics and masklist-easylist of oblivios-platform stay local; they are not published (owner). (4) main of oblivios-platform was force-pushed on 2026-11-16 (ADR-243); the old commits stay reachable by id on the remote host and the owner accepts that instead of recreating the repository.

2Why and evidence

The gate asked for an SBOM of the published components. A list that nobody can check is weak, so each statement of it is either computed from the files or compared with the record that makes it, and a mismatch stops the build; the claim review uses the same build where a claim is a number or a row of a table and a reading where it is prose.

3Consequences

Fixes of the review: the platform NOTICE named 12 patched projects and 149 files, the patches change 218 files in 18 projects (licence evidence read at the baseline 2026100600, not 2026091900); it lacked the prebuilt exitd, the 40 AOSP files of the DeviceSettings contract (Apache-2.0, Google copyright), and the MPL-2.0 and PDDL-1.0 terms of the address data, and counted three prebuilt binaries where four are committed.

The services NOTICE said 552 fetched packages (548 from crates.io and 4 in-tree), lacked the notice of the SecLists word list (MIT; the text equals the recorded hash) and the Public Suffix List (MPL-2.0), and did not name the apiguardian-api that the JUnit POMs declare; exit-daemon/README.md said four patches, there are six. The overlay index of oblivios-manifest listed 4 of 19 patch packages, the platform README 8.

SECURITY.md named a key user id ObliviOS Security; the key says FreeholdOS Security (the fingerprint was right). The classifier record said no flag artwork ships; the Data Map ships flags. The exitd record called its source commit unpushed; it is on master. licensing-and-branding-review.md named the product AegisOS. datamap/PUBLICATION-EXCLUDE.txt contradicted ADR-241 and is removed.

The READMEs now say that cited records may be unpublished and that earlier names remain in old records.

Findings that are not fixed and need the owner: five advisories that OSV lists on 2026-11-16 and no record assesses (crypto-bigint 0.5.5, ctutils 0.4.2, libsqlite3-sys 0.37.0, rustix 1.1.4, tokio 1.53.1; fixed versions exist), all in the Cargo.lock of exit-daemon that the prebuilt exitd of 2026-11-10 was built from (which of them the binary links has not been computed; the lock is to be updated and the binary rebuilt); the owner's domain of the private OTA server stands in three files of oblivios-platform (README, SOURCE.md, the OTA patch) although the docs publication scan treats it as forbidden; a frameworks/base patch modifies ReferenceGlobalRootComponent.kt, which does not exist at the pinned revision; seven of 18 upstream projects have no licence file at their root (their licence is read from file headers); the source of exit-daemon differs from the commit of its binary by 23 files.

The SBOM does not claim the linked subset of the Rust packages, the reproducibility of the binaries (stated by their records, not re-run), a legal opinion, or an aggregated licence text.

4Review when

A commit is added to a published repository (the SBOM names the commits and is rebuilt); OSV lists a new advisory or a package is yanked; the owner changes a licence or publication decision; the owner offers a binary, which brings the full public-beta gates (ADR-171).

Read from docs/governance/decision-log.md, entry ADR-244.