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.

Giant Stopwatch

arpruss

v1.310.2 MBAndroid API 4+

Gitalchemy

Thomas Pedot

v1.3.013 MBAndroid 7.0+

Githo

Glitchy-Tozier

v1.3.422.6 MBAndroid API 16+

Gitling

Maneesha Cooray

v1.0.5233.4 MBAndroid 6.0+

GitNote

Wiiznokes

v26.05.122.5 MBAndroid 11+

GitSync

ViscousPot

v1.8.6022 MBAndroid 7.0+

glmark2

glmark2

v2023.019.5 MBAndroid API 16+

Global Send

Peer Topeer

v0.2.033.3 MBAndroid 8.0+

Glucosio

Glucosio Project

v1.3.0-FOSS8.1 MBAndroid API 16+

GLXY

Andrés Villarreal

v2.31.3 MBAndroid API 14+
📷

Glyfen

talixodev

v1.081.8 MBAndroid 8.0+

GlyphPort

SebiAi

v2.0.36.6 MBAndroid 12+

Gobandroid

ligi

v2.5.92.3 MBAndroid API 9+

gobandroid ai gnugo

ligi

v2.1.24.8 MBAndroid API 15+

Goblim

Mob-Dev

v2.81.9 MBAndroid API 15+

Godot Editor 3

The Godot Foundation

v3.6.2.stable30.2 MBAndroid 5.0+

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