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 | (no flag indicated) |
| Anti-Feature: Ads | Flag if ads present | No ads indicated | (no flag indicated) |
| Anti-Feature: NonFreeAssets | Flag if ships nonfree media/assets | Not established; requires audit | / (unknown) |
| Protocols vs client license | Protocols can be FOSS even if client isn’t | Protocols MIT; Android client is source-available, not FOSS | (blocks inclusion) |