get-random-values 4.1.0

`window.crypto.getRandomValues` with fallback to Node.js crypto

get-random-values@4.1.0 was published on 2025-10-15. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is 20 || 22 || >=24.

All get-random-values versions · Permanent reference to 4.1.0 · View npm registry JSON · Latest release

Package specifications

Version4.1.0
License declarationMIT
Published2025-10-15T15:33:21.099Z
Node.js requirement20 || 22 || >=24
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size6.96 KiB
Published file count6
Package typeNot declared
ES module entryNot declared
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars18
Repository forks7

Install get-random-values 4.1.0

npm install get-random-values@4.1.0
pnpm add get-random-values@4.1.0
yarn add get-random-values@4.1.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.

Binary-Artifacts10/10 — no binaries found in the repo
Maintained10/10 — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Code-Review0/10 — Found 0/21 approved changesets -- score normalized to 0
Pinned-Dependencies10/10 — all dependencies are pinned
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions10/10 — GitHub workflow tokens follow principle of least privilege
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection3/10 — branch protection is not maximal on development and all release branches
Packaging10/10 — packaging workflow detected
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness