Vendor log monitor
Every day we check Google's public software logs, and a few others, to make sure nothing in them was rewritten or quietly left out. Last run 2026-10-14 16:35 UTC. Signed results: statements.json.
Logs
| Log | Entries | Since our last check | Last new entry | Witness signatures | Copies seen elsewhere |
|---|---|---|---|---|---|
| Pixel factory images developers.google.com/android/binary_transparency/0 | 1,192 | no change | 7 days ago | 0 | 15 (9 at this size) |
| Google system APKs (pre-March) developers.google.com/android/binary_transparency/google1p/0 | 134 | no change | 198 days ago | 0 | 15 (14 at this size) |
| Google system APKs gstatic.com/android/binary_transparency/google1p/jwt/0 | 263 | no change | 2 days ago | 0 | — |
| Google APKs, 2026/01 shard gstatic.com/android/binary_transparency/google1p/apk/2026/0 | 1,797,152 | no change | 34 days ago | 0 | — |
| Google APKs, 2026/02 shard android.transparency.goog/google1p/apk/2026/1 | 639,367 | grew, history intact 604,352 → 639,367 | today | 5 | — |
| Mainline modules, 2026/01 shard gstatic.com/android/binary_transparency/mainline/modules/2026/0 | 818 | no change | 49 days ago | 0 | — |
| Mainline modules, 2026/02 shard android.transparency.goog/mainline/modules/2026/1 | 418 | no change | today | 5 | — |
| log.frem.sh log.frem.sh | 15,879 | grew, history intact 15,142 → 15,879 | today | 1 | — |
| notbefore.net notbefore.net/log | 1,244 | grew, can't fully check 1,198 → 1,244 | no date served | 1 | — |
History intact: the log proved today's version starts with exactly what we saw last time. Can't fully check: the log doesn't publish the data that proof needs, so we can only catch it shrinking or showing two different versions at the same size.
Does everyone see the same log?
| Log | Copies collected | At the newest size | Two versions at one size | Copies that don't line up |
|---|---|---|---|---|
| developers.google.com/android/binary_transparency/0 | 15 | 9 | 0 | 0 |
| developers.google.com/android/binary_transparency/google1p/0 | 15 | 14 | 0 | 0 |
| go.sum database tree | 16 | 7 | 0 | 0 |
| tlog.andxor.it | 15 | 1 | 0 | 0 |
| log2025-1.rekor.sigstore.dev | 1 | 1 | 0 | 0 |
| transparency.dev/armored-witness/firmware_transparency/prod/1 | 15 | 14 | 0 | 0 |
| Armory Drive Prod 2 | 15 | 15 | 0 | 0 |
We collect copies of each log's state from the transparency.dev distributor and witness.gdbsecurity.com. Two different versions at the same size would mean someone is being shown a fake.
Certificate Transparency logs: all 71 that publish their data as tiles match what we rebuild from that data.
Is everything there?
- Pixel 6 and newer factory images on Google's download page: 963 in the log under the phone's own name, 157 only under a generic name, 0 missing.
- Armored Witness firmware: 28 entries, and they add up to the signed state. Every GitHub release has an entry, and every entry matches its release.
Open problems
- warn 157 Pixel images are filed only under a generic name, so a phone checking itself with its own fingerprint won't find them. since 2026-09-15