{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifrolzacgdisjmj7rctz3qasnxivlgmmztefsyyzciwiwumyb3o6a",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mmiz3kmlcr32"
  },
  "path": "/t/maintaining-our-own-appverifier-directory/38085?page=2#post_21",
  "publishedAt": "2026-05-23T07:03:42.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "jonah:\n\n> It’s been brought up that maybe we could simply release a fork with an expanded internal database too,\n\nI think a fork that you guys maintain, that we can contribute to would be a great idea.\n\njonah:\n\n> but I am not sure because I would think people will want to obtain AppVerifier from Accrescent, and we couldn’t publish a fork there (at least not yet).\n\nThis is long winded, but as I can’t read code. I typically download most apks from github and check their SHA256 code they provide, against the apk I have downloaded. Then check it against AppVerifier as well as uploading it to VirusTotal before I install.\n\nThat’s just me, but I think if you released it on Github and listed the apks SHA256 for people to verify. I think people here trust you and your Team enough that might satisfy them.",
  "title": "Maintaining our own AppVerifier directory"
}