crypto-hash alternatives and similar modules
Based on the "Security" category.
Alternatively, view crypto-hash alternatives based on common mentions on social networks and blogs.
-
snyk
DISCONTINUED. Snyk CLI scans and monitors your projects for security vulnerabilities. [Moved to: https://github.com/snyk/cli] -
rate-limiter-flexible
Atomic and non-atomic counters and rate limiting tools. Limit resource access at any scale. -
Varlock
.env files built for sharing powered by @env-spec decorator comments run anywhere with any language, plus deeper integrations for next.js, vite, and more. -
Themis by Cossack Labs
Easy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms. -
is-website-vulnerable
finds publicly known security vulnerabilities in a website's frontend JavaScript libraries -
-
-
-
-
-
jose-simple
DISCONTINUED. Jose-Simple allows the encryption and decryption of data using the JOSE (JSON Object Signing and Encryption) standard. -
SaaSHub - Software Alternatives and Reviews
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of crypto-hash or a related project?
README
crypto-hash
Tiny hashing module that uses the native crypto API in Node.js and the browser
Useful when you want the same hashing API in all environments. My cat calls it isomorphic.
In Node.js it uses require('crypto'), while in the browser it uses window.crypto.
The browser version is only ~300 bytes minified & gzipped.
When used in the browser, it must be in a secure context (HTTPS).
This package is for modern browsers. IE11 is not supported.
Install
npm install crypto-hash
Usage
import {sha256} from 'crypto-hash';
console.log(await sha256('🦄'));
//=> '36bf255468003165652fe978eaaa8898e191664028475f83f506dabd95298efc'
API
sha1(input, options?)
sha256(input, options?)
sha384(input, options?)
sha512(input, options?)
Returns a Promise<string> with a Hex-encoded hash.
In Node.js, the operation is executed using worker_threads. A thread is lazily spawned on the first operation and lives until the end of the program execution. It's unrefed, so it won't keep the process alive.
SHA-1 is insecure and should not be used for anything sensitive.
input
Type: string ArrayBuffer ArrayBufferView
options
Type: object
outputFormat
Type: string\
Values: 'hex' | 'buffer'\
Default: 'hex'
Setting this to buffer makes it return an ArrayBuffer instead of a string.
Related
- hasha - Hashing in Node.js made simple