electron-fingerprints
Advanced tools
Generates fingerprints for electron version detection by downloading electron releases and generating checksums of the files contained in each release.
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.
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.
All Stable electron releases for the following architectures are fingerprinted:
A list of release fingerprints is under the hashes directory.
Released under WTFPL.
FAQs
Fingerprints of various files for all electron releases
The npm package electron-fingerprints receives a total of 2 weekly downloads. As such, electron-fingerprints popularity was classified as not popular.
We found that electron-fingerprints demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
TC39 met in Seattle and advanced 9 JavaScript proposals, including three to Stage 4, introducing new features and enhancements for a future ECMAScript release.
Security News
Deno 2.2 enhances Node.js compatibility, improves dependency management, adds OpenTelemetry support, and expands linting and task automation for developers.
Security News
React's CRA deprecation announcement sparked community criticism over framework recommendations, leading to quick updates acknowledging build tools like Vite as valid alternatives.
