@aws-crypto/sha256-browserv5.2.0

latest

Top 10k

Copy SHA256

License: Permissive (Apache-2.0)

Published:

SHA256 wrapper for browsers that prefers `window.crypto.subtle` but will fall back to a pure JS implementation in @aws-crypto/sha256-js to provide a consistent interface for SHA256.

Pass

Info: Completed

Everything is awesome!

SAFE Assessment

Compliance

Licenses

No license compliance issues

Secrets

No sensitive information found

Security

Vulnerabilities

No known vulnerabilities detected

Hardening

No application hardening issues

Threats

Tampering

No evidence of software tampering

Malware

No evidence of malware inclusion

Issues

No issues found

Behaviors

See all behaviors

Uses cryptographical functions.

packer

Contains multi-line comments.

behavior

Vulnerabilities

Downloads

1.6B

Recorded Downloads Since 2021

Maintenance

Contibutors

Dependencies

Declared Dependencies

Dependents

1.67K

Dependents

Issues per Version Graph

Scanned

FAQ for @aws-crypto/sha256-browser

What is @aws-crypto/sha256-browser?

SHA256 wrapper for browsers that prefers `window.crypto.subtle` but will fall back to a pure JS implementation in @aws-crypto/sha256-js to provide a consistent interface for SHA256. For more information about this package, visit its homepage.

Is @aws-crypto/sha256-browser malicious or is it safe to use?

The npm package @aws-crypto/sha256-browser was scanned for malware, software tampering, risky behaviors, exposed secrets and known vulnerabilities. No risks were detected, therefore, this version of the package is currently considered as safe to use.

Is @aws-crypto/sha256-browser popular?

The npm package @aws-crypto/sha256-browser ranks among the top 10000 projects in this community. It has 2B recorded downloads. A package's popularity is not a good indicator of its safety, visit the SAFE Assessment section to see the full analysis of package deployment risk categories.

How do I secure @aws-crypto/sha256-browser once it is in my app?

Since we can't know when or where malicious attacks will happen, we recommend tracking how @aws-crypto/sha256-browser behaviors change over multiple software releases. By adopting differential analysis in your release process, you can detect unexpected changes to a @aws-crypto/sha256-browser version, which can prevent advanced software supply chain attacks. Read how our technology can help prevent future attacks similar to SolarWinds and 3CX.