Skip to content
Find publicly accessible magento files that identify a version
Branch: master
Clone or download
Latest commit d978ace Oct 31, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
md5sums Update version hashes Oct 31, 2018
.gitignore
README.md Remove redundant shell scripts and update README with ports Jun 5, 2017
find_unique_checksums.py Add all hashes, not just static files Jun 5, 2017
generate_md5sums.py EE 1.9.1.1 release has an odd leading path Jun 6, 2017
version_hashes.json

README.md

Magento Version Identification

Hashes of static files can be used to determine the version of a remote Magento installation. Measured in 2015, this resulted in an accurate version identification for 91,7% of 220,000 tested Magento installations worldwide.

See the resulting hashes

This repo does:

  • Generate md5sum from static files of Magento releases
  • Calculate the best set of checksums, optimized for coverage and speed (find the right version with the least amount of requests).

The original idea was discussed here.

How to rebuild the winning fingerprints

To get accurate results, you need a complete archive of Magento tar.gz files. There is no single source to mirror, so you would have to:

  1. Use a Magento partner account to mirror recent Community and Enterprise releases. The magento-downloader tool could help.
  2. You can find older releases here:
wget -r -l 1 -nc -nd -P sources --reject '*latest.tar.gz' -A '*.gz' http://magento.mirror.hypernode.com/releases/

Place releases in the sources folder, in ce-full and ee-full subfolders. Then run generate_md5sums.py (takes a few minutes) and find_unique_checksums.py which will calculate a new version_hashes.json for you.

Contributors

Thanks to Steve Robbins, Sjoerd Langkemper and Ryan Dewhurst!

This code has been ported:

You can’t perform that action at this time.