crypto-random-string 3.3.1

Generate a cryptographically strong random string

crypto-random-string@3.3.1 was published on 2021-02-12. Its manifest declares 1 runtime dependency and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=8.

All crypto-random-string versions · Permanent reference to 3.3.1 · Latest release

Package specifications

Version3.3.1
License declarationMIT
Published2021-02-12T10:16:47.305Z
Node.js requirement>=8
Type declarationsNot declared
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size13.97 KiB
Published file count5
Package typeNot declared
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars591
Repository forks43

Install crypto-random-string 3.3.1

npm install crypto-random-string@3.3.1
pnpm add crypto-random-string@3.3.1
yarn add crypto-random-string@3.3.1

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-Review4/10 — Found 14/30 approved changesets -- score normalized to 4
Pinned-Dependencies0/10 — dependency not pinned by hash detected -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
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
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Security-Policy10/10 — security policy file detected
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-Protection0/10 — branch protection not enabled on development/release branches
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness