Store App Audit: Android apps compared with Google Play
Store App Audit is an open source desktop program that compares Android apps with their public listings on Google Play: the apps on a connected phone, in a list or in a folder of APK files. It tells you which ones cannot be found on Google Play in the country you choose, which have a listing that has not been updated for a long time and which versions are behind the one on Google Play. It is for anyone who wants to know whether the apps they use, archive or keep an eye on are still maintained; the code and the published releases are on GitHub.
Store App Audit is free and open source, under the GPL-3.0-only licence.
Updated on
Operating systems: Windows, Linux, macOS
What it checks
Store App Audit takes a list of Android apps and, for each one, looks for its public listing on Google Play. If you also have a version of the app, the one installed on the phone or the one in a file, it compares it with the version Google Play shows. It reports:
- Availability: it looks for the listing in the Google Play country you choose, because an app can be available in one country and not in another. ‘Not Found’ means that it found no listing in the configured countries it managed to check; it does not prove that the app has disappeared from Google Play worldwide.
- Listing age: it helps you find apps whose listing has not been updated for a long time. The status is ‘Recent’ up to 365 days, ‘Aging’ from 366 to 730, ‘Stale’ beyond 730; these are the default thresholds and you can change them. ‘Anomaly’ flags Google Play responses that are unusual, incomplete or impossible to classify with confidence.
- Version: it classifies the version you have, against the one on Google Play, as ‘Match’, ‘Outdated’, ‘Newer’, ‘Different’, ‘Device Specific’ or ‘Unknown’. The comparison is cautious: ‘Outdated’ appears only when the version data establishes which one comes first. Staged and device-specific rollouts can still give a different result from a simple comparison with the public listing.
- Category: since version 2.3 it reports the category of the listing on Google Play, in the results, in saved filters and in exports.
- The Maintenance Score, if you turn it on: it sums up the maintenance signals in a number from 0 to 100. It is a heuristic: how it is calculated is explained in the program’s Help menu. It is not a rating of malware, security or trustworthiness.
- Changes over time: it compares previous audits and phone snapshots, and shows, by group, what has changed in the list of apps, in availability on Google Play, in listings that have reappeared, in versions and in updates.
How it works
It is a desktop program with a graphical interface. You start it, choose where to take the apps from, confirm the Google Play country and run the audit. You can filter the results with search, by status and with filters you can save. Selecting a row shows the data the result rests on: from Google Play, from the phone, from the file.
You can export the results, all of them or only the visible ones, as CSV, HTML or JSON with a versioned schema. Since version 2.2 the same audits can also be run from the command line, without the graphical interface, with the result in JSON or CSV.
The apps can come from three sources:
- An Android phone connected to the computer. The program reads it through ADB (Android Debug Bridge), read-only: it lists the packages, reads the device and app metadata, and can open the screen with an app’s details on the phone. USB debugging must be on and the device must be authorised. If ADB is missing on the computer, on supported systems the program offers to download Google’s official Platform-Tools.
- A list of apps. A CSV, TSV or TXT file with the package identifiers, one per line or in a
package_namecolumn. You need neither the phone nor the app files. - Files on the computer.
.apk,.apks,.apkmand.xapkfiles, chosen one by one or found in a folder and its subfolders. Each file stays a result of its own, even when several files belong to the same app. The program can rename them, one at a time or in bulk with a full preview, and, on your command, can delete those that are outdated or unknown, with safeguards before permanent deletion, as well as byte-for-byte identical copies.
What stays on the computer and what goes online
Imported files, phone data, settings, the cache, audit history, snapshots and activity logs are processed and stored on your computer. Store App Audit has no telemetry or analytics service of its own.
An audit, however, does not run entirely offline. To look up the listings, the program sends the package identifiers, the country and the language to Google Play’s public addresses. App icons, if you turn them on, are downloaded from the HTTPS addresses Google Play provides. The program’s update check queries GitHub’s public API for published releases. Google’s Platform-Tools are downloaded only if you approve it.
Diagnostic files are created only if you ask for them and are not sent automatically. They may contain data from the computer or the phone: read them through before sharing them.
What it is not
- It is not a Google product: it is not affiliated with or endorsed by Google.
- It is not an Android app: it is a desktop program. It only reads the phone’s apps: it does not install, uninstall, enable, disable or otherwise modify them.
- It does not give a security verdict: the Maintenance Score is not a rating of malware, security or trustworthiness.
- It does not prove that an app has been removed from Google Play: ‘Not Found’ holds for the countries the program managed to check.
- It is not an SEO tool: it lies outside my work on websites. I publish it under MRC Labs, the brand of my software.
How to get it
The code is public on GitHub, in the mrc-labs/PlayStoreAppAudit repository. The repository keeps its earlier name for compatibility; the program is called Store App Audit.
The latest published release is 2.3.0, of 5 October 2026, for Windows (x64 and ARM64), Linux (x64 and ARM64) and macOS (Intel and Apple Silicon). The first, 1.0.0, dates from 17 August 2026.
Release 2.3.0 is published in the repository as ZIP archives, one per system and architecture, with a SHA256SUMS.txt file to verify what you download. The Windows and Linux archives are not signed; the macOS ones have only an ad hoc development signature and are not notarised. That is why Windows, with SmartScreen, and macOS may ask you to confirm before starting it: this depends on the signing status, not on an error in the program. Production signing is deferred to a later release.
As long as the archives are not signed, this page links not to the files to download but to the repository, where you will find the code, the instructions and the published releases.
The code is licensed under the GNU General Public License version 3 (GPL-3.0-only). Commercial use is allowed under the terms of the licence; for anyone who needs rights the GPLv3 does not give, such as proprietary redistribution or integration into a closed-source product, a commercial licence may be available. Third-party components remain under their own licences.
It is written in Python, with Qt 6 (PySide6) for the interface: the repository’s README explains how to run it from source. Bugs and suggestions are reported in the repository. Contributions are welcome, under the rules in CONTRIBUTING.md; substantial ones require acceptance of the Contributor License Agreement (CLA).
Frequently asked questions about Store App Audit
Does Store App Audit change the apps on my phone?
No. It reads the phone through ADB, read-only: it lists the packages and reads the metadata. It does not install, uninstall, enable or disable apps.
Does it tell me whether an app is safe?
No. It looks at maintenance signals: whether the listing exists, how long it has gone without an update, whether the version is behind. The Maintenance Score, from 0 to 100, is not a rating of malware, security or trustworthiness.
If an app comes out as ‘Not Found’, has it been removed from Google Play?
Not necessarily. ‘Not Found’ means that the program found no listing in the configured countries it managed to check. An app can be available in one country and not in another, so the result does not prove that it has disappeared everywhere.
Does my phone’s data leave the computer?
In part. To look up the listings, the program sends Google Play the package identifiers of the apps you check, with the country and the language. The phone’s data, the audit history and the settings are processed and stored on the computer, and the program has no telemetry.
Where do I download it?
From the repository on GitHub, where the code and the releases are published. The archives do not yet have a production signature: that is why this page leads to the repository and not straight to the files to download.
If you have a website
Store App Audit lies outside SEO. To find out how search engines and AI assistants read your site, there are the free tools of MRC Labs. To fix what they find, get in touch: I’ll reply personally and, if needed, we’ll arrange a call.