Gathering detailed insights and metrics for argon2
Gathering detailed insights and metrics for argon2
Gathering detailed insights and metrics for argon2
Gathering detailed insights and metrics for argon2
npm install argon2
Typescript
Module System
Min. Node Version
Node Version
NPM Version
93.5
Supply Chain
99.5
Quality
81
Maintenance
100
Vulnerability
99.6
License
JavaScript (77.91%)
C++ (22.09%)
Total Downloads
30,286,004
Last Day
12,659
Last Week
245,599
Last Month
1,145,669
Last Year
12,495,590
1,902 Stars
741 Commits
96 Forks
17 Watching
13 Branches
43 Contributors
Minified
Minified + Gzipped
Latest Version
0.41.1
Package Id
argon2@0.41.1
Unpacked Size
846.14 kB
Size
315.29 kB
File Count
33
NPM Version
10.8.2
Node Version
20.17.0
Publised On
31 Aug 2024
Cumulative downloads
Total Downloads
Last day
-76%
12,659
Compared to previous day
Last week
-7.8%
245,599
Compared to previous week
Last month
-2.1%
1,145,669
Compared to previous month
Last year
58%
12,495,590
Compared to previous year
3
5
Bindings to the reference Argon2 implementation.
Want to use it on the command line? Instead check node-argon2-cli.
It's possible to hash using either Argon2i, Argon2d or Argon2id (default), and verify if a password matches a hash.
To hash a password:
1const argon2 = require('argon2'); 2 3try { 4 const hash = await argon2.hash("password"); 5} catch (err) { 6 //... 7}
To see how you can modify the output (hash length, encoding) and parameters (time cost, memory cost and parallelism), read the wiki
To verify a password:
1try { 2 if (await argon2.verify("<big long hash>", "password")) { 3 // password match 4 } else { 5 // password did not match 6 } 7} catch (err) { 8 // internal failure 9}
See this article on the wiki for steps on how to migrate your existing code to Argon2. It's easy!
A TypeScript type declaration file is published with this module. If you are using TypeScript 2.0.0 or later, that means you do not need to install any additional typings in order to get access to the strongly typed interface. Simply use the library as mentioned above.
1import * as argon2 from "argon2"; 2 3const hash = await argon2.hash(..);
node-argon2 provides prebuilt binaries from v0.26.0
onwards. They are
built every release using GitHub Actions.
The current prebuilt binaries are built and tested with the following systems:
Binaries should also work for any version more recent than the ones listed above. For example, the binary for Ubuntu 20.04 also works on Ubuntu 22.04, or any other Linux system that ships a newer version of glibc; the binary for MacOS 11 also works on MacOS 12. If your platform is below the above requirements, you can follow the Before installing section below to manually compile from source. It is also always recommended to build from source to ensure consistency of the compiled module.
You can skip this section if the prebuilt binaries work for you.
You MUST have a node-gyp global install before proceeding with the install, along with GCC >= 5 / Clang >= 3.3. On Windows, you must compile under Visual Studio 2015 or newer.
node-argon2 works only and is tested against Node >=18.0.0.
To install GCC >= 5 on OSX, use homebrew:
1$ brew install gcc
Once you've got GCC installed and ready to run, you then need to install node-gyp, you must do this globally:
1$ npm install -g node-gyp
Finally, once node-gyp is installed and ready to go, you can install this library, specifying the GCC or Clang binary to use:
1$ CXX=g++-12 npm install argon2
NOTE: If your GCC or Clang binary is named something different than g++-12
,
you'll need to specify that in the command.
1$ npx @mapbox/node-pre-gyp rebuild -C ./node_modules/argon2
Run @mapbox/node-pre-gyp
instead of node-gyp
because node-argon2's
binding.gyp
file relies on variables from @mapbox/node-pre-gyp
.
You can omit npx @mapbox
and use just node-pre-gyp
if you have a global
installation of @mapbox/node-pre-gyp
, otherwise prefixing npx
will use
the local one in ./node_modules/.bin
You can do either of the two methods below:
1$ npm install argon2 --build-from-source
node-argon2
install script and build manually.1$ npm install argon2 --ignore-scripts 2$ npx node-gyp rebuild -C ./node_modules/argon2
This seems to be an issue related to snap (see #345 (comment)). Installing Node with another package manager, such as asdf or nvm, is a possible workaround.
The interface of both are very similar, notably, node-argon2-ffi splits the
argon2i and argon2d function set, but this module also has the argon2id option,
which node-argon2-ffi does not support. Also, while node-argon2-ffi
suggests you promisify crypto.randomBytes
, node-argon2 library does that
internally.
node-argon2 is much lighter than node-argon2-ffi, at 184 KB for argon2@0.29.1 against 2.56 MB for argon2-ffi@1.2.0. Performance-wise, the libraries are equal. You can run the same benchmark suite if you are curious, but both can perform around 130 hashes/second on an Intel Core i5-4460 @ 3.2GHz with default options.
This library is implemented natively, meaning it is an extension to the node engine. Thus, half of the code is C++ bindings, the other half is Javascript functions. node-argon2-ffi uses ffi, a mechanism to call functions from one language in another, and handles the type bindings (e.g. JS Number -> C++ int).
This project exists thanks to all the people who contribute. [Contribute].
Become a financial contributor and help us sustain our community. [Contribute]
Support this project with your organization. Your logo will show up here with a link to your website. [Contribute]
Work licensed under the MIT License. Please check P-H-C/phc-winner-argon2 for license over Argon2 and the reference implementation.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
10 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
Reason
packaging workflow detected
Details
Reason
0 existing vulnerabilities detected
Reason
SAST tool is not run on all commits -- score normalized to 7
Details
Reason
dependency not pinned by hash detected -- score normalized to 5
Details
Reason
Found 3/20 approved changesets -- score normalized to 1
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
Project has not signed or included provenance with any releases.
Details
Score
Last Scanned on 2024-12-16
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More