Skip to content

Publisher

F-Droid

Verified publisher

F-Droid is a catalogue of free and open-source Android software. It builds apps from their published source and signs the results itself, then publishes the signing certificate and a SHA-256 for every build — which is why we can import from it without weakening what a listing here is supposed to mean. Apps imported from F-Droid are grouped under this profile for provenance; each one credits its own author, who wrote it.

3217

apps listed

Apps from F-Droid

Each listing below carries the hash and certificate fingerprint for its current build. Because these apps share a publisher, they also share a signing key — which means a build that claims to come from F-Droid but presents a different fingerprint is telling you something useful.

ownCloud

F-Droid

v4.8.213.9 MBAndroid 7.0+

OwnTracks

F-Droid

v2.5.912.9 MBAndroid 7.0+
📝

p!n

F-Droid

v1.2.132.9 MBAndroid API 16+

Pachli for Mastodon

Pachli

v3.7.230.7 MBAndroid 6.0+

packlist

F-Droid

v0.132.4 MBAndroid API 14+

PadConnect

Ishan

v0.6.24.5 MBAndroid 10+

Padland

F-Droid

v3.63.2 MBAndroid 6.0+

Pagan

Quintin Smith

v1.8.1913.9 MBAndroid 8.1+

Page

Bizzle

v1.20 MBAndroid 5.0+

PAIesque

OJ Random

v9046.9 MBAndroid 14+

Panoramicon

Daniel Kraft

v1.1.115.2 MBAndroid 13+

Pantry

Enrico Frigo

v0.1.12-fdroid3.4 MBAndroid 8.0+

Paper Loop

Eve-146T

v1.0.032.7 MBAndroid 10+

Paper Loop 2

Eve-146T

v1.0.132.7 MBAndroid 10+

PaperKnife+

F-Droid

v1.17.8 MBAndroid 7.0+

Paperless Share

Quinn Casey

v1.1.420.1 MBAndroid API 16+

Page 85 of 135

Definition

What “verified publisher” means here

It is a claim about identity, not about quality. A verified publisher on APKBrowse has demonstrated two things: that they control the domain their software ships from, and that they control the signing key their builds are signed with. We check the second against the first — a build arriving from the publisher's own release channel, signed with the key we already have on file for them, is one we can attribute with confidence.

That attribution is the whole point. Once a certificate fingerprint is recorded against a publisher, every later release can be checked against it, and anything signed with a different key stops looking like an update and starts looking like a different app wearing the same name. Android enforces this rule at install time regardless of what we say — it will refuse an update signed with a key that does not match the version already on the device. We are simply making the fingerprint visible before you get that far.

What the badge does not mean: that we have audited the code, that we endorse the app, or that the privacy policy is any good. Those are separate questions, and a verified publisher can still ship something you would rather not install. Verification tells you who wrote it. Deciding whether to trust them is still yours.