We open every app before we list it.
The facts on an app page come from our own look at the download, not from what the maker told us. Here is what we look at, and what a check does not prove.
What we look at
- We fetch the real downloadThe maker gives us the same .dmg or .zip that buyers get, as a link or an upload. We record its SHA-256 fingerprint, so anyone can later confirm they have the exact file we checked.
- Who signed itWe read the code signature inside the app: the Developer ID name and the Apple team behind it. An unsigned app is shown as unsigned.
- Whether Apple notarized itWe look for Apple's notarization ticket. Notarized means Apple scanned that build and issued a ticket for it.
- A malware scanWe scan the download with ClamAV, an open-source malware scanner, using its current definitions.
- What it can reachWe read the entitlements: whether the app is sandboxed, whether the hardened runtime is on, and what file access it asks for.
- What it is built fromWhich Macs it runs on (Apple silicon, Intel), the oldest macOS it supports, and whether it is a native app or wraps a web view.
- That the file belongs to the listingThe app's name, bundle identifier and signer are compared with the listing and with earlier versions. A file that does not match is held back and never shown as checked.
- It stays within the rulesA listing goes public once the maker has proved the site is theirs. We read listings after they go up and remove any that break the rules or misdescribe the app.