nemo
/
which-electron
mirror of https://github.com/captn3m0/which-electron.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
Try to find out which Electron version is bundled in an application file.
17 Commits 3 Branches 17 Tags 386 KiB
JavaScript 93.4%
PHP 6.2%
Makefile 0.4%
Go to file
Nemo e674c15ad0 Functional for zip files! 2021-07-16 20:16:29 +05:30
.github/workflows Add GitHub Actions for test 2021-07-16 12:33:40 +05:30
_scripts Adds tests for os file list guesser 2021-07-16 12:27:39 +05:30
tests Find a list of files worth hashing 2021-07-16 19:45:02 +05:30
.editorconfig Initial commit 2021-07-15 20:56:36 +05:30
.gitignore Initial commit 2021-07-15 20:56:36 +05:30
HACKING.md Add note about generating fixtures 2021-07-16 12:42:09 +05:30
LICENSE Initial commit 2021-07-15 20:56:36 +05:30
README.md Functional for zip files! 2021-07-16 20:16:29 +05:30
finder.js Find a list of files worth hashing 2021-07-16 19:45:02 +05:30
fingerprint.js Functional for zip files! 2021-07-16 20:16:29 +05:30
index.js Functional for zip files! 2021-07-16 20:16:29 +05:30
os.js Add tests for os detection from filename 2021-07-16 12:01:47 +05:30
package-lock.json Functional for zip files! 2021-07-16 20:16:29 +05:30
package.json Functional for zip files! 2021-07-16 20:16:29 +05:30
utils.js Initial commit 2021-07-15 20:56:36 +05:30
versions.json Change supported.json to list all versions 2021-07-16 19:27:43 +05:30
zip.js Functional for zip files! 2021-07-16 20:16:29 +05:30

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
Version Constraint: <v7.0.0
Multiple guesses from fingerprinting:
[
  'v3.1.10', 'v3.1.11',
  'v3.1.12', 'v3.1.13',
  'v3.1.5',  'v3.1.6',
  'v3.1.7',  'v3.1.8',
  'v3.1.9'
]

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

$ which-electron Google.Play.Music.Desktop.Player.deb

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. (WIP)
  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.

License

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