vintprox

Wherever the app’s code is on. I usually go around finding the link in the store page or through the search engine. Most of the time, they end up on GitHub and GitLab, sometimes on Codeberg or other instance.

Paranoid section ahead: Don’t blindly trust the issues list, closed or open, because there are still ways to permanently delete those, hence giving bad actor a way to hide evidence of the on-going security problem.

I look at the latest release date. At leisure time, I would also go and check repository and issue tracker to see whether something serious is being ignored. If it’s crucial for business, I would spare time investigating the source code itself.

I would not necessarily say that many apps uploaded to F-Droid and other repositories are unsafe, because I don’t have all that energy to audit anything I use. What helps me to stay on the safe side is reading into things - enclosed descriptions and names may look like a small factor to some, once they tread the sources, but it saves me both the time and trouble. Sloppily written stuff usually implies a sloppy code, a lax attention to details on the developer’s side.

Wow, that’s quite useful.

It is rare that everything app like this has a source code available to public. I’m immediately hooked, as someone who can’t wrap his head around making custom views in Obsidian and its open source alternatives. (For the love of Pete, frontmatters are just too demanding on syntax department!) Fork, stat! 😃

License doesn’t seem to step on your toes as long as you don’t distribute Anytype in exchange for something (w/ or w/o modifications).