electron-fingerprints - npm Package Compare versions

Comparing version 1.0.0 to 1.1.0

package.json

 {
   "name": "electron-fingerprints",
-  "version": "1.0.0",
+  "version": "1.1.0",
   "description": "Fingerprints of various files for all electron releases",
-  "main": "lookup.json",
+  "main": "index.js",
   "repository": {
@@ -10,2 +10,5 @@ "type": "git",
   },
+  "scripts": {
+    "test": "node test.js"
+  },
   "keywords": [
@@ -12,0 +15,0 @@ "electron",

README.md

@@ -1,4 +0,4 @@
-# electron-fingerprints
+# [electron-fingerprints](https://www.npmjs.com/package/electron-fingerprints) ![npm bundle size](https://img.shields.io/bundlephobia/minzip/electron-fingerprints) ![npm](https://img.shields.io/npm/v/electron-fingerprints) ![NPM](https://img.shields.io/npm/l/electron-fingerprints) ![Zero Dependencies](https://img.shields.io/badge/Dependencies-Zero-blue)
 
-Generates fingerprints for electron version detection by downloading electron releases and generating checksums of the files contained in each release.
+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.
 
@@ -13,6 +13,21 @@ ## why
 
+## install
+
+```shell
+npm install electron-fingerprints
+```
+
 ## usage
 
-This is just the raw data files, see [which-electron][we] for a usable package. The `lookup.json` file is published as the `electron-fingerprints` package on NPM.
+This is just the raw data files, see [which-electron][we] for a usable package. The `lookup.json` file is published as the `electron-fingerprints` package on NPM. Programmatic usage is still possible:
 
+```javascript
+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.
+
 ## supported releases
@@ -23,11 +38,68 @@
 - 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.
 
-## LICENSE
+## 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.
 
 [we]: https://github.com/captn3m0/which-electron

New alerts

Trivial Package

Supply chain risk

Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency.

Found 1 instance in 1 package

Fixed alerts

Empty package

Supply chain risk

Package does not contain any code. It may be removed, is name squatting, or the result of a faulty package publish.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

2506378

increased by30.81%

Number of package files

10

increased by100%

Lines of code

8

increased byInfinity%

Number of lines in readme file

103

increased by232.26%

No dependency changes