This is an F-Droid style repository for Android apps, provided by IzzyOnDroid. Applications in this repository are official binaries built by the original application developers, taken from their resp. repositories (mostly Github).
If you are an open-source developer and wish your app(s) included, be welcome to contact me. Ways to do that can be found e.g. from the Imprint at the IzzyOnDroid Android site.
If you still wish to use this repository with your F-Droid client, this is the URL you should use to add it:
If you want to make sure it's the right one (and nobody played with DNS). you
can use additionally enter this fingerprint in the appropriate field of your F-Droid client:
Or, both combined (as the QR code on the main page does it):
From time to time, I check on Github for repositories featuring Android apps
which are not part of the main F-Droid repository, but have
files along with the code. If such an app seems useful, has been updated not
too long ago (at least within the last 12 month), and seems legit, I take a raw
look at the
.apk file (do the permissions look appropriate, are
there and „crazy indicators“ making it look strange) – and if it passes, it
I also checked on GitLab a few times, but couldn't find more than a few repos also offering
.apk files with their tags.
Of course I won't find them all: some serve their
along with the
releases/ (which I favor), some simply have them
amongst the repository files (acceptable), some do not have any at all, and
I'm afraid I've missed a lot. So I'm open to suggestions. Good candidates
meet most of the following criteria:
.apkfiles must be available.
.apkfiles are preferably located in the
releases/tree at Github resp. the
tags/tree at GitLab and are properly tagged. In this case, I can catch updates automatically.
.apksize should not be too big. 2-5 MB are fine, up to 10 MB is acceptable. Above 10 MB are exceptions (must be a real good reason here), and my current „hard limit“ is 20 MB.
If you know an app that would fit those criteria but is not listed in this repo (nor in the official one), you're welcome to visit the repo’s GitLab presence (where the full conditions are listed, so please make sure to read them first) and file an issue (please use the template, which is preselected; you can reset it if you instead need to file an issue for a problem you experience with this repo), specifying the necessary details.
Read between the lines above: if the
.apk files were served in
tags/ tree and are properly tagged for all versions, I
have a script that runs automatically in regular intervalls to check for and download
updates. For those apps, it works pretty well. Some other apps must be checked
manually, which I don't do on a regular base (but those are few).
Usually up to 3 versions per app are kept in the repository, but in sum they shall not occupy much more than 20 M per app (see „hard limit“ above). If a newer version is released after that, the oldest version is automatically purged. And no, I currently do not plan keeping a second „Archive Repo“ for older versions.
This indeed may happen. Apps might get „kicked out“ if it gets obvious something „bad“ slipped in – e.g. by users reporting bad behavior of an app installed from here.
I might also decide to drop an app which hasn't been updated for more than
a year, no longer provides
.apk files despite of new releases,
or lost its value for other reasons (e.g. the service behind it went out of
business). But generally, I plan no „purge actions for dubios reasons“.
Especially I don't have the policy of excluding Ad-Blockers and the like ;)
Another reason for an app getting removed from my repo is if it was added to the „official F-Droid repository“. Removal then mainly is to avoid confusion at the users' end, due to signature mismatch on updates (if they installed an app from the official repo, signed with F-Droid's key, and an update rolls in earlier via my repo – which is usually the case – there'd be a warning displayed if they'd try to apply that update). In some cases an app still stays with my repo; usually it then uses reproducible builds so there'd be no signature mismatch.
For this, two actions are taken:
Apps are scanned for malware, using the services of VirusTotal. VirusTotal currently runs more than 50 engines to check files, which is quite some coverage. However, results differ between engines: some are more prone to „false positives“ than others, and some even report ads as malware (we might tend to agree on that). So results might look different – and here's how they are presented for each file:
Except for the „pending“ shield, the label will always link to the corresponding detail page at the VirusTotal website. Feel encouraged to check that. If a file is marked by a yellow or red shield, also check the app's description, which might hold further hints. Sometimes a finding might be „normal“ (e.g. a vulnerability test suite could easily trigger a „false alert“, as described above). Moreover, some scanners thread a „PUA“ (potentially unwanted addon/application) as alert – as indicated above.
APK files are also checked for libraries they are using. This is done locally, using LibRadar (plus some additions of mine). Findings are grouped into three categories:
You will not only find the categories and names of libraries, but also some additional details: which permissions are found accessed by them is the most interesting part here. Where available, a link is given to their resp. websites/pages. Additionally, for most of the libraries there're additional details available, indicated by an icon and revealed by clicking on it: