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.

Sentinel Lens

F-Droid

v1.0.294.1 MBAndroid 11+

Sentry

lucky

v1.1.24.5 MBAndroid 6.0+

Seqular

Seqular Network

v2.3.14.7 MBAndroid 6.0+
💬

SerialPipe

wh201906

vv0.0.32.1 MBAndroid API 17+

SerialTest

wh201906

vV0.3.539 MBAndroid 5.0+
💬

ServeIt

Vignesh Nandakumar

v2.0.020.7 MBAndroid API 16+

ServerBox

lollipopkit

v1.0.134039.8 MBAndroid 7.0+

SexyTopo

Rich Smith

v1.12.26.9 MBAndroid 6.0+

SFTP-SAF

Alain Knaff

v0.2.228.8 MBAndroid 8.0+

Shaarlier

Dimtion

v1.8.01.5 MBAndroid API 15+

Shader Editor

Markus Fisch

v2.36.23.4 MBAndroid 6.0+
💬

Shadowsocks

shadowsocks

v5.3.5-nightly14.1 MBAndroid 6.0+
💬

Shadowsocks

shadowsocks

v5.3.5-nightly13.9 MBAndroid 6.0+

Share Paste O2

F-Droid

v2024.12.209.8 MBAndroid 8.0+

Share to Clipboard

F-Droid

v1.15.01.2 MBAndroid API 15+

ShareAsQR

Mikulas Heinz

v1.0.31.1 MBAndroid 7.0+

ShareX

F-Droid

v2.3.86.7 MBAndroid 5.0+

Sheepy Horn

Mendhak

v50.9 MBAndroid 6.0+

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