Home / Verify it
Verify it
You do not have to take any of this on trust. Five links join GrapheneOS to what you can check on your own machine, and you hold the last one.
The five links
Upstream
A GrapheneOS manifest tag, copied byte for byte.
Patch
Patch packages on that baseline.
Decision
The decision log names each patch set.
Bill of materials
Every component, licence and file hash.
You
Rebuild it. The two must match byte for byte.
1. Upstream
oblivios-manifest holds the pinned GrapheneOS and AOSP revisions that the patches apply to, and how each baseline was chosen. They are copied byte for byte from a GrapheneOS manifest tag. The upstream baseline in the published bill of materials is manifest 2026100600.
2. Patch
oblivios-platform holds the patch packages: ObliviOS added to GrapheneOS source. Each patch keeps the licence of the upstream file it changes, and the packages carry provenance records (SOURCE.md). Three components are committed as prebuilt files, exitd, libvault_core.so and airpods-core.jar, each with its source commit, toolchain, build command and SHA-256. oblivios-services holds the platform-independent logic and native daemons those binaries come from.
3. Decision
The decision log is one table in which one entry is one long line, about 760 KB in all. Do not open it whole. Find an entry by its number:
# find one entry grep -n '^| ADR-214 ' docs/governance/decision-log.md
The columns are ID, date, decision, status, rationale, consequences and the trigger that reopens it. A decision changes only through a new entry that names what it supersedes.
4. Bill of materials
sbom/ holds a CycloneDX 1.6 document and an SPDX 2.3 document, a SHA-256 for every file of the four repositories, and the registry and upstream evidence they were built from. It describes these commits:
oblivios-manifest9d8ef6f73726oblivios-platform1f42fcb9c3dfoblivios-services70f6fd024de5
oblivios-docs is a snapshot without history; its files are in files.sha256.
5. You
Clone the four repositories side by side at those commits. In the folder that holds them, run:
# 1. every file against its SHA-256
sha256sum -c oblivios-docs/sbom/files.sha256
# 2. rebuild the documents and compare
python3 oblivios-docs/tools/sbom/build-sbom.py \
--root . --docs oblivios-docs \
--evidence oblivios-docs/sbom/evidence \
--check oblivios-docs/sbom The second command rebuilds both documents from the same commits and compares them byte for byte. It fails when a file, a hash, a commit, a licence or a claim of a NOTICE file is not supported. The documents validate against the official CycloneDX 1.6 and SPDX 2.3 schemas.
What the bill of materials does not claim
- Rust:
Cargo.locklists every package any configuration may resolve. Which subset a given binary links has not been computed. - Upstream: only the projects that the patches modify are listed, with their licence evidence.
- The reproducibility of the prebuilt binaries is stated by their records. It was not re-run for the bill of materials.
- Vulnerabilities are those that OSV listed on the day named in the evidence file.
- No legal opinion: the licence of a component is what its publisher states.