Generates fingerprints for electron version detection by downloading electron releases and generating checksums of the files contained in each release.

Go to file

Nemo 6d995537f4 [docs] Mention supported releases		2021-07-16 02:30:37 +05:30
hashes	Commit initial data	2021-07-16 02:27:20 +05:30
.npmignore	Additional code and docs	2021-07-16 00:10:24 +05:30
HACKING.md	Additional code and docs	2021-07-16 00:10:24 +05:30
LICENSE	Initial commit 💥	2021-07-15 23:50:42 +05:30
README.md	[docs] Mention supported releases	2021-07-16 02:30:37 +05:30
fingerprint.php	Additional code and docs	2021-07-16 00:10:24 +05:30
lookup-table.php	Commit initial data	2021-07-16 02:27:20 +05:30
lookup.json	Commit initial data	2021-07-16 02:27:20 +05:30
package.json	Additional code and docs	2021-07-16 00:10:24 +05:30
versions.txt	Initial commit 💥	2021-07-15 23:50:42 +05:30

README.md

electron-fingerprints

Generates fingerprints for electron version detection by downloading electron releases and generating checksums of the files contained in each release.

why

You can use this to guess which electron version is being used in a given application. A given electron version is (almost always) tightly bound to a node and chrome release as well, so you get a better sense of what the application is running.

Written as the backend for which-electon.

usage

This is just the raw data files, see which-electron for a usable package. The lookup.json file is published as the electron-fingerprints package on NPM.

supported releases

All Stable electron releases for the following architectures are fingerprinted:

linux-x64
darwin-x64 (Mac OS)
win32-x64 (Windows)

A list of release fingerprints is under the hashes directory.

LICENSE

Released under WTFPL.