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

Go to file

Nemo 66d091626b new releases		2022-03-05 14:02:50 +05:30
.github/workflows	Move to multiple smaller lookup tables	2021-07-18 17:07:14 +05:30
hashes	new releases	2022-03-05 14:02:50 +05:30
lookup	new releases	2022-03-05 14:02:50 +05:30
.editorconfig	new releases	2022-03-05 14:02:50 +05:30
.gitignore	New release	2022-01-13 12:29:02 +05:30
.npmignore	ignore Makefile for npm package	2022-02-21 21:02:52 +05:30
HACKING.md	Document the schema structure	2021-11-24 14:51:46 +05:30
LICENSE	Initial commit 💥	2021-07-15 23:50:42 +05:30
Makefile	new releases	2022-03-05 14:02:50 +05:30
README.md	v2021.12.19	2021-12-19 15:02:43 +05:30
fingerprint.php	add comment about missing versions	2022-02-02 18:51:41 +05:30
index.js	Move lookup tables to separate directory	2021-07-18 17:18:41 +05:30
lookup-table.php	New electron releases	2021-08-09 16:56:22 +05:30
package-lock.json	2022.2.21	2022-02-21 21:02:05 +05:30
package.json	2022.2.21	2022-02-21 21:02:05 +05:30
test.js	new electron releases	2022-02-02 18:13:28 +05:30

README.md

electron-fingerprints

Generates fingerprints for electron version detection by downloading electron releases and generating checksums (sha1 hashes) of the files contained in each release. Published as a lookup table on NPM.

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.

install

npm install electron-fingerprints

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. Programmatic usage is still possible:

const lookup = require("electron-fingerprints");
// baf786083f482c1f035e50e105b5f7475af1e00b = sha1(ffmpeg.dll)
lookup["win32-x64"]["baf786083f482c1f035e50e105b5f7475af1e00b"];
// ["v1.4.3", "v1.4.4", "v1.4.5"]

You can sort or filter the returned versions if needed. If you'd like to access the raw data, see HACKING.md for a schema description.

supported releases

All Stable electron releases for the following architectures are fingerprinted:

linux-x64
linux-arm64
darwin-x64 (Mac OS)
win32-x64 (Windows)
win32-arm64 (Windows)
darwin-arm64 (Apple Silicon)

A list of release fingerprints is under the hashes directory. Releases made when Electron was still called atom-shell are not supported (Before April 2015).

versioning

Starting from 2021.12.19 release, releases are versioned by YYYY.MM.DD format.

which files are present?

Here's a count of the most common extensions present across all releases:

   1620 dat
   1620 version
   1650 LICENSE
   1744 Current
   1744 Resources
   1762 so
   1830 html
   1844 PkgInfo
   1944 modulemap
   2202 dylib
   2354 js
   2437 asar
   3237 bin
   4272 Helper
   6142 plist
   6224 dll
  34235 Electron
  45360 h
  84596 pak

.pak files are currently excluded from the lookup table, but the other files should be easily usable. While lookup up, try to get hashes from the following extensions:

.h
.dll
.plust
.Helper
.bin
.asar
.dylib
.so
.plist
Electron Framework
Electron Helper
Electron Helper (GPU)
Electron Helper (Plugin)
Electron Helper (Renderer)
electron
(GPU)
(Plugin)
(Renderer)

which-electron uses the following extensions and filenames to fingerprint:

.h, .dll, .bin, .asar, .dylib, .so, .exe
electron framework, squirrel, electron, electron helper, chrome_100_percent, chrome_200_percent

license

Released under WTFPL.