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.

Xmp Mod Player

F-Droid

v4.12.02.6 MBAndroid API 14+

XMPP Admin

j.r

v1.02.4 MBAndroid API 15+

Xournal++

TheOneWithTheBraid

v1.1.1120.2 MBAndroid API 19+

Xray

SaeedDev94

v12.3.041.5 MBAndroid 8.0+

XrayFA

Q7DF1

v1.6.326.6 MBAndroid 9.0+
🎬

XScreenSaver

jwz

v6.0980.7 MBAndroid API 18+

YA Habit Tracker

Zaved

v0.4.13.5 MBAndroid 8.0+

YAACC

F-Droid

v5.2.08.5 MBAndroid 8.1+

yadaw

MLM Games

v0.9.28 MBAndroid 10+

Yagni Launcher

F-Droid

v0.8.4-alpha2.6 MBAndroid 7.0+

YAM

F-Droid

v1.11.2 MBAndroid 6.0+

YARC

Julien Stephan

v1.23.5 MBAndroid 5.0+

Yatoo

F-Droid

v0.12.13.3 MBAndroid 5.1+

Yeeemp

pegasko

v1.0092.1 MBAndroid 5.0+

YidKey KD

deadlockz

v1.11.6 MBAndroid API 16+

Yokatta

F-Droid

vv0.3.47.2 MBAndroid 10+

Yoke

F-Droid

v0.1.20 MBAndroid 5.0+

Page 133 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.