It does not have a FLOSS licence in the first place and it’s not completely open source.
So it has to use one of the licenses listed here in this example: F-Droid Search: image , and must rely entirely on open-source software.
However, it looks like some Anti-Features are still allowed, right?
So, in other words, as long as the app is fully open-source, relies only on opensource dependencies, includes certain anti-features, and keeps its original license unmodified, it’s acceptable?
So for my guess, the license Anytype uses is a no go for f-droid…
Anytype has it’s own licence. Anti features or not, the licence itself wouldn’t be allowed in the first place.
The F-Droid repo is where all these licenses are required. There are other, less restrictive repositories available, as well as an option of self-hosting one.
Although, the request here is for inclusion into the F-Droid store and not just “make AnyType available IN F-Droid”, sadly.
Seems like.. Anytype won’t be added to the f-droid store.
| Checkpoint | F-Droid requirement | Anytype Android (anytype-kotlin) | Result |
|---|---|---|---|
| App license is FOSS (OSI/FSF-approved) | OSI/FSF-approved free/open-source license required for main repo | “Any Source Available License 1.0” with noncommercial + “Allowed Networks” limits | |
| Commercial use allowed | Commercial use and redistribution permitted | Only noncommercial, or commercial use limited to whitelisted networks | |
| Unrestricted redistribution/modification | No field-of-use or network restrictions | Network whitelist and consent from “Any Association” | |
| Buildable from public source | Source public and reproducibly buildable | Public repo exists; build plausible but license blocks main repo | |
| No mandatory proprietary SDKs | No closed SDKs/services required to build | Not established here; needs audit | |
| Backend is self-hostable/configurable | Prefer easy user reconfiguration to FOSS backend | “Allowed Networks” suggests centralized authorization | |
| Eligible for main F-Droid repo | Must satisfy FOSS licensing and build rules | Fails due to non-FOSS client license | |
| Anti-Feature: NonFreeNet (if relicensed) | Flag if relies on controlled/nonfree network | Likely if default/realistic use needs authorized network without easy user reconfig | |
| Anti-Feature: Tracking | Flag if tracking present | No evidence of trackers from available info | |
| Anti-Feature: Ads | Flag if ads present | No ads indicated | |
| Anti-Feature: NonFreeAssets | Flag if ships nonfree media/assets | Not established; requires audit | |
| Protocols vs client license | Protocols can be FOSS even if client isn’t | Protocols MIT; Android client is source-available, not FOSS |