ObliviOS Developer portal Project site

Home / Components / Verify

Verify

Rebuild the SBOM from the same commits and compare it byte for byte, and see how each prebuilt binary was made.

Prebuilt binaries

Three binaries are committed to oblivios-platform. Each says what it was built from and with what, so you can build it again and compare the hash.

airpods-core.jar

airpods/core/airpods-core.jar

SHA-256

8658fb35e5c03f4c8741704886a1446e661a2b5abb253b02945aa59e4002f2f8

Size
35.8 KB
Built from
services airpods-core at b5e73ab164ec, the current source
Toolchain
Gradle 9.6.1, Java 21 toolchain, ./gradlew :airpods-core:jar --offline
Reproduced
Per the record: two builds, same SHA-256; not re-run by this build

exitd

privacy/exit/daemon/arm64/exitd

SHA-256

d5dca624755f9a40f9cc3bcf19b2cf4fd485f1a1c4b5c21e8fd3f917d1119e63

Size
19.4 MB
Built from
services exit-daemon at c9139fe9363c, not the current source: the tree has changed since
Toolchain
AOSP prebuilts/rust-toolchain 1.93.1, aarch64-linux-android, cargo build --release --locked --offline
Reproduced
Per the record: two builds, same SHA-256; not re-run by this build

libvault_core.so

passwords/core/arm64/libvault_core.so

SHA-256

2f5d7f2f19c643211df3700b9af8e4ad74c10341914fc8a38199fdb5c5f525a3

Size
1.9 MB
Built from
services vault-core at b5e73ab164ec, not the current source: the tree has changed since
Toolchain
AOSP prebuilts/rust-toolchain 1.93.1, aarch64-linux-android, cargo build --release --locked --offline
Reproduced
Per the record: two builds, same SHA-256; not re-run by this build

Check it yourself

Clone the four repositories side by side at these commits, then run both commands from the directory that holds them.

oblivios-manifest
0cfaafa823604a1e508ee484ad1cbbf8bf64d221
oblivios-platform
c1ff1d71e410cf5ebdb8d380f4cc25859bae7868
oblivios-services
1110f95581d3ce31aee0f1318ce96e1c04ac9e41
oblivios-docs
A snapshot without history; its files are in files.sha256.
Upstream baseline
2026100600
sha256sum -c oblivios-docs/sbom/files.sha256
python3 oblivios-docs/tools/sbom/build-sbom.py \
    --root . --docs oblivios-docs \
    --evidence oblivios-docs/sbom/evidence \
    --check oblivios-docs/sbom

The first command compares every file with its recorded SHA-256. The second rebuilds both documents from the same commits and the evidence files, compares them byte for byte, and fails on any fact that the files do not support.

Read from sbom/README.md and sbom/oblivios.cdx.json.

What the SBOM does not claim

  • Rust: Cargo.lock lists every package that any configuration may resolve. The subset linked into one binary has not been computed.
  • npm: the packages are build-time tools. The static output of oblivios.org holds two font families and no script of any package.
  • The reproducibility of the prebuilt binaries is stated by their records. It was not run again here.
  • No legal opinion: the licence of a component is what its publisher states.