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-11-19 17:35 UTC. Signed results: statements.json.

Logs

LogEntriesSince our last checkLast new entryWitness signaturesCopies seen elsewhere
Pixel factory images
developers.google.com/android/binary_transparency/0
1,452no change2 days ago0—
Google system APKs (pre-March)
developers.google.com/android/binary_transparency/google1p/0
134no change234 days ago0—
Google system APKs
gstatic.com/android/binary_transparency/google1p/jwt/0
283no change16 days ago0—
Google APKs, 2026/01 shard
gstatic.com/android/binary_transparency/google1p/apk/2026/0
1,797,152no change70 days ago0—
Google APKs, 2026/02 shard
android.transparency.goog/google1p/apk/2026/1
1,195,292grew, history intact 1,156,493 → 1,195,292today5—
Mainline modules, 2026/01 shard
gstatic.com/android/binary_transparency/mainline/modules/2026/0
818no change85 days ago0—
Mainline modules, 2026/02 shard
android.transparency.goog/mainline/modules/2026/1
1,357no changetoday5—
log.frem.sh
log.frem.sh
76,231grew, history intact 75,810 → 76,231today2—
notbefore.net
notbefore.net/log
1,432grew, can't fully check 1,432 → 1,432no date served1—

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?

LogCopies collectedAt the newest sizeTwo versions at one sizeCopies that don't line up

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.

Is everything there?

Open problems