The tweetnacl npm package is a port of NaCl, the Networking and Cryptography library, to JavaScript. It provides a set of cryptographic primitives for encryption, decryption, signing, and verification. It is designed to be easy to use and to have a high level of security.
Public-key authenticated encryption
This feature allows for secure message exchange between two parties using public-key cryptography. The code sample demonstrates how to encrypt and decrypt a message using a pair of public and private keys.
const nacl = require('tweetnacl');
const naclUtil = require('tweetnacl-util');
const keyPairA = nacl.box.keyPair();
const keyPairB = nacl.box.keyPair();
const nonce = nacl.randomBytes(nacl.box.nonceLength);
const message = naclUtil.decodeUTF8('Secret Message');
const encrypted = nacl.box(message, nonce, keyPairB.publicKey, keyPairA.secretKey);
const decrypted = nacl.box.open(encrypted, nonce, keyPairA.publicKey, keyPairB.secretKey);
const decryptedMessage = naclUtil.encodeUTF8(decrypted);Secret-key authenticated encryption
This feature provides a way to encrypt and decrypt messages using a shared secret key. The code sample shows how to perform authenticated encryption and decryption with a nonce and a single key.
const nacl = require('tweetnacl');
const naclUtil = require('tweetnacl-util');
const secretKey = nacl.randomBytes(nacl.secretbox.keyLength);
const nonce = nacl.randomBytes(nacl.secretbox.nonceLength);
const message = naclUtil.decodeUTF8('Secret Message');
const encrypted = nacl.secretbox(message, nonce, secretKey);
const decrypted = nacl.secretbox.open(encrypted, nonce, secretKey);
const decryptedMessage = naclUtil.encodeUTF8(decrypted);Digital signatures
This feature allows for the creation and verification of digital signatures. The code sample demonstrates how to sign a message and verify the signature using a public and private key pair.
const nacl = require('tweetnacl');
const naclUtil = require('tweetnacl-util');
const keyPair = nacl.sign.keyPair();
const message = naclUtil.decodeUTF8('Verify this message');
const signature = nacl.sign.detached(message, keyPair.secretKey);
const isVerified = nacl.sign.detached.verify(message, signature, keyPair.publicKey);Hashing
This feature provides a way to compute a cryptographic hash of a message. The code sample shows how to hash a message and encode the hash in base64.
const nacl = require('tweetnacl');
const naclUtil = require('tweetnacl-util');
const message = naclUtil.decodeUTF8('Hash this message');
const hash = nacl.hash(message);
const hashHex = naclUtil.encodeBase64(hash);libsodium-wrappers is a set of wrappers around libsodium, which is a portable, cross-compilable, installable, packageable fork of NaCl. It offers similar functionalities to tweetnacl but with additional features and performance optimizations.
forge is a native implementation of TLS in JavaScript and tools to work with ASN.1, X.509, PKCS, TLS, and more. It is more comprehensive than tweetnacl, providing a wider range of cryptographic operations, including certificate handling and secure networking.
crypto-js is a growing collection of standard and secure cryptographic algorithms implemented in JavaScript. It focuses on hashing and encryption and provides a different API than tweetnacl, with a focus on ease of use for common cryptographic tasks.
Port of TweetNaCl / NaCl to JavaScript for modern browsers and Node.js. Public domain.
Demo: https://dchest.github.io/tweetnacl-js/
The primary goal of this project is to produce a translation of TweetNaCl to JavaScript which is as close as possible to the original C implementation, plus a thin layer of idiomatic high-level API on top of it.
There are two versions, you can use either of them:
nacl.js is the port of TweetNaCl with minimum differences from the
original + high-level API.
nacl-fast.js is like nacl.js, but with some functions replaced with
faster versions. (Used by default when importing NPM package.)
TweetNaCl.js has been audited by Cure53 in January-February 2017 (audit was sponsored by Deletype):
The overall outcome of this audit signals a particularly positive assessment for TweetNaCl-js, as the testing team was unable to find any security problems in the library. It has to be noted that this is an exceptionally rare result of a source code audit for any project and must be seen as a true testament to a development proceeding with security at its core.
To reiterate, the TweetNaCl-js project, the source code was found to be bug-free at this point.
[...]
In sum, the testing team is happy to recommend the TweetNaCl-js project as likely one of the safer and more secure cryptographic tools among its competition.
You can install TweetNaCl.js via a package manager:
Yarn:
$ yarn add tweetnacl
NPM:
$ npm install tweetnacl
You can find usage examples in our wiki.
All API functions accept and return bytes as Uint8Arrays. If you need to
encode or decode strings, use functions from
https://github.com/dchest/tweetnacl-util-js or one of the more robust codec
packages.
In Node.js v4 and later Buffer objects are backed by Uint8Arrays, so you
can freely pass them to TweetNaCl.js functions as arguments. The returned
objects are still Uint8Arrays, so if you need Buffers, you'll have to
convert them manually; make sure to convert using copying: Buffer.from(array)
(or new Buffer(array) in Node.js v4 or earlier), instead of sharing:
Buffer.from(array.buffer) (or new Buffer(array.buffer) Node 4 or earlier),
because some functions return subarrays of their buffers.
Implements x25519-xsalsa20-poly1305.
Generates a new random key pair for box and returns it as an object with
publicKey and secretKey members:
{
publicKey: ..., // Uint8Array with 32-byte public key
secretKey: ... // Uint8Array with 32-byte secret key
}
Returns a key pair for box with public key corresponding to the given secret key.
Encrypts and authenticates message using peer's public key, our secret key, and the given nonce, which must be unique for each distinct message for a key pair.
Returns an encrypted and authenticated message, which is
nacl.box.overheadLength longer than the original message.
Authenticates and decrypts the given box with peer's public key, our secret key, and the given nonce.
Returns the original message, or null if authentication fails.
Returns a precomputed shared key which can be used in nacl.box.after and
nacl.box.open.after.
Same as nacl.box, but uses a shared key precomputed with nacl.box.before.
Same as nacl.box.open, but uses a shared key precomputed with nacl.box.before.
Length of public key in bytes.
Length of secret key in bytes.
Length of precomputed shared key in bytes.
Length of nonce in bytes.
Length of overhead added to box compared to original message.
Implements xsalsa20-poly1305.
Encrypts and authenticates message using the key and the nonce. The nonce must be unique for each distinct message for this key.
Returns an encrypted and authenticated message, which is
nacl.secretbox.overheadLength longer than the original message.
Authenticates and decrypts the given secret box using the key and the nonce.
Returns the original message, or null if authentication fails.
Length of key in bytes.
Length of nonce in bytes.
Length of overhead added to secret box compared to original message.
Implements x25519.
Multiplies an integer n by a group element p and returns the resulting
group element.
Multiplies an integer n by a standard group element and returns the resulting
group element.
Length of scalar in bytes.
Length of group element in bytes.
Implements ed25519.
Generates new random key pair for signing and returns it as an object with
publicKey and secretKey members:
{
publicKey: ..., // Uint8Array with 32-byte public key
secretKey: ... // Uint8Array with 64-byte secret key
}
Returns a signing key pair with public key corresponding to the given
64-byte secret key. The secret key must have been generated by
nacl.sign.keyPair or nacl.sign.keyPair.fromSeed.
Returns a new signing key pair generated deterministically from a 32-byte seed.
The seed must contain enough entropy to be secure. This method is not
recommended for general use: instead, use nacl.sign.keyPair to generate a new
key pair from a random seed.
Signs the message using the secret key and returns a signed message.
Verifies the signed message and returns the message without signature.
Returns null if verification failed.
Signs the message using the secret key and returns a signature.
Verifies the signature for the message and returns true if verification
succeeded or false if it failed.
Length of signing public key in bytes.
Length of signing secret key in bytes.
Length of seed for nacl.sign.keyPair.fromSeed in bytes.
Length of signature in bytes.
Implements SHA-512.
Returns SHA-512 hash of the message.
Length of hash in bytes.
Returns a Uint8Array of the given length containing random bytes of
cryptographic quality.
Implementation note
TweetNaCl.js uses the following methods to generate random bytes, depending on the platform it runs on:
window.crypto.getRandomValues (WebCrypto standard)window.msCrypto.getRandomValues (Internet Explorer 11)crypto.randomBytes (Node.js)If the platform doesn't provide a suitable PRNG, the following functions, which require random numbers, will throw exception:
nacl.randomBytesnacl.box.keyPairnacl.sign.keyPairOther functions are deterministic and will continue working.
If a platform you are targeting doesn't implement secure random number
generator, but you somehow have a cryptographically-strong source of entropy
(not Math.random!), and you know what you are doing, you can plug it into
TweetNaCl.js like this:
nacl.setPRNG(function(x, n) {
// ... copy n random bytes into x ...
});
Note that nacl.setPRNG completely replaces internal random byte generator
with the one provided.
Compares x and y in constant time and returns true if their lengths are
non-zero and equal, and their contents are equal.
Returns false if either of the arguments has zero length, or arguments have
different lengths, or their contents differ.
TweetNaCl.js supports modern browsers that have a cryptographically secure pseudorandom number generator and typed arrays, including the latest versions of:
Other systems:
Install NPM modules needed for development:
$ npm install
To build minified versions:
$ npm run build
Tests use minified version, so make sure to rebuild it every time you change
nacl.js or nacl-fast.js.
To run tests in Node.js:
$ npm run test-node
By default all tests described here work on nacl.min.js. To test other
versions, set environment variable NACL_SRC to the file name you want to test.
For example, the following command will test fast minified version:
$ NACL_SRC=nacl-fast.min.js npm run test-node
To run full suite of tests in Node.js, including comparing outputs of JavaScript port to outputs of the original C version:
$ npm run test-node-all
To prepare tests for browsers:
$ npm run build-test-browser
and then open test/browser/test.html (or test/browser/test-fast.html) to
run them.
To run tests in both Node and Electron:
$ npm test
To run benchmarks in Node.js:
$ npm run bench
$ NACL_SRC=nacl-fast.min.js npm run bench
To run benchmarks in a browser, open test/benchmark/bench.html (or
test/benchmark/bench-fast.html).
For reference, here are benchmarks from MacBook Pro (Retina, 13-inch, Mid 2014) laptop with 2.6 GHz Intel Core i5 CPU (Intel) in Chrome 53/OS X and Xiaomi Redmi Note 3 smartphone with 1.8 GHz Qualcomm Snapdragon 650 64-bit CPU (ARM) in Chrome 52/Android:
| nacl.js Intel | nacl-fast.js Intel | nacl.js ARM | nacl-fast.js ARM | |
|---|---|---|---|---|
| salsa20 | 1.3 MB/s | 128 MB/s | 0.4 MB/s | 43 MB/s |
| poly1305 | 13 MB/s | 171 MB/s | 4 MB/s | 52 MB/s |
| hash | 4 MB/s | 34 MB/s | 0.9 MB/s | 12 MB/s |
| secretbox 1K | 1113 op/s | 57583 op/s | 334 op/s | 14227 op/s |
| box 1K | 145 op/s | 718 op/s | 37 op/s | 368 op/s |
| scalarMult | 171 op/s | 733 op/s | 56 op/s | 380 op/s |
| sign | 77 op/s | 200 op/s | 20 op/s | 61 op/s |
| sign.open | 39 op/s | 102 op/s | 11 op/s | 31 op/s |
(You can run benchmarks on your devices by clicking on the links at the bottom of the home page).
In short, with nacl-fast.js and 1024-byte messages you can expect to encrypt and authenticate more than 57000 messages per second on a typical laptop or more than 14000 messages per second on a $170 smartphone, sign about 200 and verify 100 messages per second on a laptop or 60 and 30 messages per second on a smartphone, per CPU core (with Web Workers you can do these operations in parallel), which is good enough for most applications.
See AUTHORS.md file.
crypto_authsealed boxesSome notable users of TweetNaCl.js:
FAQs
Port of TweetNaCl cryptographic library to JavaScript
The npm package tweetnacl receives a total of 13,324,563 weekly downloads. As such, tweetnacl popularity was classified as popular.
We found that tweetnacl 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
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.