sha.js 2.3.3
streaming sha1 hash in pure javascript
sha.js@2.3.3 was published on 2015-01-12. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All sha.js versions · Permanent reference to 2.3.3 · Latest release
Package specifications
| Version | 2.3.3 |
|---|---|
| License declaration | MIT |
| Published | 2015-01-12T19:05:09.251Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 1 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | Not declared |
| Direct advisories | 1 |
| Resolved graph dependencies | 1 |
| Repository stars | 298 |
| Repository forks | 63 |
Install sha.js 2.3.3
npm install sha.js@2.3.3 pnpm add sha.js@2.3.3 yarn add sha.js@2.3.3
Runtime dependencies
- inherits ^2.0.1
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.
- inherits@2.0.4 — direct
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.
Known direct advisories
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Code-Review | 1/10 — Found 4/27 approved changesets -- score normalized to 1 |
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 9/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 10/10 — security policy file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/sha.js/2.3.3 — retrieved 2026-10-29T14:51:34.226Z
- https://api.deps.dev/v3/projects/github.com%2Fcrypto-browserify%2Fsha.js — retrieved 2026-10-29T05:59:59.275Z (stale snapshot; refresh pending)
- https://api.deps.dev/v3/systems/npm/packages/sha.js/versions/2.3.3 — retrieved 2026-10-29T14:51:34.725Z
- https://api.deps.dev/v3/systems/npm/packages/sha.js/versions/2.3.3:dependencies — retrieved 2026-10-29T14:51:34.750Z