@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.

@aws-crypto/sha256-browser@5.2.0 was published on 2023-10-16. Its manifest declares 7 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @aws-crypto/sha256-browser versions · Permanent reference to 5.2.0

Package specifications

Version5.2.0
License declarationApache-2.0
Published2023-10-16T19:44:49.151Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count7
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size42.04 KiB
Published file count41
Package typeNot declared
ES module entry./build/module/index.js
Default entry./build/main/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies10
Repository stars69
Repository forks35

Install @aws-crypto/sha256-browser 5.2.0

npm install @aws-crypto/sha256-browser@5.2.0
pnpm add @aws-crypto/sha256-browser@5.2.0
yarn add @aws-crypto/sha256-browser@5.2.0

Runtime dependencies

Peer requirements

  • None declared

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review9/10 — Found 19/21 approved changesets -- score normalized to 9
Maintained3/10 — 4 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 3
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Binary-Artifacts10/10 — no binaries found in the repo
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies4/10 — dependency not pinned by hash detected -- score normalized to 4
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection8/10 — branch protection is not maximal on development and all release branches
Security-Policy10/10 — security policy file detected
SAST4/10 — SAST tool is not run on all commits -- score normalized to 4

Evidence and freshness