Nemo
949d12789c
Based on https://github.com/captn3m0/electron-fingerprints/#which-files-are-present |
||
---|---|---|
.github/workflows | ||
_scripts | ||
tests | ||
.editorconfig | ||
.gitignore | ||
HACKING.md | ||
LICENSE | ||
README.md | ||
finder.js | ||
fingerprint.js | ||
index.js | ||
os.js | ||
package-lock.json | ||
package.json | ||
utils.js | ||
versions.json | ||
zip.js |
README.md
which-electron
Try to find out which Electron version is bundled inside an application.
Usage
npm install which-electron
which-electron Google.Play.Music.Desktop.Player.OSX.zip
which-electron Google.Play.Music.Desktop.Player.OSX.dmg
which-electron Google.Play.Music.Desktop.Player.deb
How does it work?
We attempt multiple pathways:
- The presence of a
electron.asar
file denotes an electron version<v7.0.0
, since later releases dropped that file and embedded it in the binary instead. - A
version
text file is sometimes included in the final binary. - The
node_modules/electron/package.json
file is sometimes present. - A lookup table of hashes from various electron releases is used to guess the version. (WIP)
- Get the electron version from the electron binary (WIP)
Note that this can be run against untrusted binaries as it does not try to run the application.
License
Licensed under the MIT License. See LICENSE file for details.