Damus
Zapstore · 1w
If we can figure this out and link to a specific APK hash, I will implement this nostr:nevent1qqsyzvwezvly0qqtepsnucxv9w2rasv84s2gant30k23s99grtgsclspzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtczyrdtd3sxt...
Juraj๐Ÿด๐Ÿ’›๐ŸŒ˜ profile picture
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 source code, not APKs. Also, the check probably won't last for long anyway, people do releases all the time.

The main thing this would tell you: "Someone looked at the code of this project at some point". And maybe short summary. So this would be something like a review, launched by reputable people (reputable - from the point of view of your Nostr account). Not "the latest APK you are going to install is up to date". Because - you would not check updates anyway. You are deciding to install an app, and when you do, you are just autoupdating anyway. Or it could tell you red flags after you install.

Very probably when you are updating, no one has launched an agent yet. And it might be smart to get updates as they come (they might fix security bugs), not wait for reviewers (that may never come!).

Ideas? Comments?
3โค๏ธ2๐Ÿค™1๐Ÿซ‚1
Zapstore · 1w
Good point, and true there are few reproducible apps. Would be nice to tag a version (as per Software Applications NIP) against which the latest analysis was run, rather than a git commit. These reports also contribute to reputation to the keystore/certificate signing the APK so they help anyway.
Leo Wandersleb · 1w
Attesting a check for a commit id is correct. Reproducers can link it to binary hashes.
flake.nix · 1w
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 i...