59fa2670ed001e8f62286eaec86153ed86a0aef6b0ad98b4e6dfeb4b11b119bd
Plugin Checksums
Every file of every published release, fingerprinted with MD5 and SHA-256. Check whether the plugin files on a site are the files we shipped — no account, no license key, no request that identifies the site being checked.
Coverage starts 14 Aug 2026. We publish checksums from the current release of each product forward, not for versions released before this service existed. If a version is not listed, we have no manifest for it — that is a gap in our coverage, not a finding about the files.
The register
8580ab52c75e56a8dcd71bc30eb440c8ab7388f14a15005ca107982332fd932f
77e2efccc934c4668d9f3c87da2e10a13087d3b6c7419187ceb656461ffe2f67
dd1e7b05d5936bb7f12d3bc7d12e4a11c4e0086ed19e8baed7f1e1e25d6db761
12e9b1cc87d43cd44d405092d37d77e87cf9cda3740fb2f091b80d5b43e8aa20
4cb249a260808b57c38f152abc05391f6493e05b8a0ace58148ccbde4015a3fb
ba8f73981cea15c0f2bdde1bda6932f1d3e18794a11e73cfc5dd2eb828643530
1184868500b6913291cd4e96287043108514e23106f8c78af6138de5e7bd10c2
2441af4234fa809022962dca0032a7f7fb3d5d1bb79d185ec9f2b1577fad2c6a
91c1317d1b498ba94c692e5bae2b329f6a556ca5d755b441191472405297c4fb
3f7ca9730e1fff1ee56f45dd0342101136a3e2d0ab1b390e945b126f34e0c461
51f50d6a5d7cd1fc20d11433c437c59a83c0fe160f29c011c434e682ba62dc22
18f48cf0174ec9cd5200096e6097bae44306bf034d5aafaf1852ff8a79180346
adc7d023e3eb90e6a0cac32af565a0ec22a48784668fc9c9eb4c43134f60e61c
bb274a22671a6aaed0824d323d3e36bf8b429a87c2934ac1c7f7e8e7ccc76a82
No product matches that.
Check a download
Hash the zip you received and compare it to the digest listed above. This tells you the archive is ours before you unpack anything.
$ shasum -a 256 azonpress.zip
59fa2670ed001e8f62286eaec86153ed86a0aef6b0ad98b4e6dfeb4b11b119bd azonpress.zip
Compare the whole string. A matching prefix means nothing on its own.
Check an installed plugin
Fetch the manifest for the version on the site and compare every file. The manifest lists
paths relative to the plugin directory, so demo-pro.php means
wp-content/plugins/demo-pro/demo-pro.php.
# every file in one released version
curl https://checksums.wpmanageninja.com/plugin-checksums/{slug}/{version}.json
# which versions exist
curl https://checksums.wpmanageninja.com/plugin-checksums/{slug}/index.json
# everything we publish
curl https://checksums.wpmanageninja.com/plugins.json
Endpoints
| Path | Returns |
|---|---|
/plugin-checksums/{slug}/{version}.json | Checksums for one release |
/plugin-checksums/1.0/?slug=…&version=… | The same, query-string form |
/plugin-checksums/{slug}/index.json | Every published version of one plugin |
/plugins.json | Every plugin listed above |
GET and HEAD only, CORS open, ETag honoured. A published
version never changes, so it is served immutable and can be cached forever.
Format
The plugin, version and files keys are byte-compatible
with the WordPress.org checksum API, so anything that already reads
downloads.wordpress.org/plugin-checksums/ reads this too. Our additions live
under _meta, where strict consumers can ignore them.
{
"plugin": "example-pro",
"version": "1.4.2",
"files": {
"example-pro.php": { "md5": "…", "sha256": "…" }
},
"_meta": {
"zipSha256": "…", // the digest listed above
"fileCount": 412,
"softChange": [ … ], // may differ without meaning tampering
"ignore": [ … ] // written after install; skip these
}
}
What this does and does not tell you
A mismatch means a file differs from what we published. That is worth investigating, but it is not proof of compromise on its own: FTP transfers in text mode rewrite line endings, and site owners sometimes patch plugins deliberately.
A clean result is narrower than it looks. It says the plugin directory matches our release. It says nothing about the rest of the site, and nothing about whether the release itself was safe. These manifests are served over TLS but are not yet signed, so they carry the same trust model as the WordPress.org checksum API.