nemo
/
which-electron
mirror of https://github.com/captn3m0/which-electron.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
which-electron/README.md

1.9 KiB
Raw Blame History

which-electron npm Libraries.io dependency status for latest release NPM

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
Version Constraint (Unsupported): <v7.0.0
Fingerprint: v3.1.7-v3.1.8
v3.1.8 is currently not supported

$ which-electron HashTag-win32-x64.zip
Found Version file: v7.1.10
v7.1.10 is currently not supported
Fingerprint: v7.1.10
v7.1.10 is currently not supported

$ which-electron Appium-linux-1.21.0.AppImage
Fingerprint: v7.2.4-v7.3.3
v7.3.3 is currently not supported

How does it work?

We attempt multiple pathways:

  1. 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.
  2. A version text file is sometimes included in the final binary.
  3. The node_modules/electron/package.json file is sometimes present.
  4. A lookup table of hashes from various electron releases is used to guess the version. In case of multiple matches, it returns a range of versions.
  5. 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. It has been tested against various file formats: zip/dmg/exe/AppImage/tar.gz etc. It extracts limited files using 7-zip.

Known Issues

It is known to not work against:

  1. Windows setup files (ones with -setup in their name)

License

Licensed under the MIT License. See LICENSE file for details.