Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@cryptography/sha512
Advanced tools
High-performance synchronous SHA-512 implementation for JavaScript. Optimized for browsers.
Package is available through npm
and yarn
npm install @cryptography/sha512
yarn add @cryptography/sha512
This package is optimized for small byte inputs (<10kb).
Also, it is highly recommended to run CPU-intensive tasks in a Web Worker.
import sha512 from '@cryptography/sha512'
const hash = sha512('Hello World!')
const bytes = sha512('Hello World!', 'array')
For hashing large files or other data chuncks use stream()
to create a hashing stream.
sha512.stream().update('Hello World!').digest();
Benchmarks:
Contributions are welcome! Contribution guidelines will be published later.
FAQs
High-performance synchronous SHA-512 implementation for JavaScript
The npm package @cryptography/sha512 receives a total of 7 weekly downloads. As such, @cryptography/sha512 popularity was classified as not popular.
We found that @cryptography/sha512 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
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.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.