Juraj🏴💛🌘
· 3w
Very nice. I'll try to tackle this somehow. A bit more community ideas before.
Questions: I would tie this to source code, not APK. Problem is most don't do reproducible builds and we probably audit ...
It might be overengineered or cluttered. But as you say, new releases come all the time, so one could imagine taking a page out of existing statis code analysis tools and keep the parts of the audit on the code that hasn't changed between versions instead of throwing out an entire audit. I imagine in the case of a messaging platform, that a folder containing ui elements would change quite often, whereas a e.g. cryptography.cpp would probably change quite infrequently.