bigint-crypto-utils 2.5.2

Utils for working with cryptography using native JS implementation of BigInt. It includes arbitrary precision modular arithmetics, cryptographically secure random numbers and strong probable prime generation/testing.

bigint-crypto-utils@2.5.2 was published on 2020-03-24. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All bigint-crypto-utils versions · Permanent reference to 2.5.2 · Latest release

Package specifications

Version2.5.2
License declarationMIT
Published2020-03-24T23:35:34.159Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size103.43 KiB
Published file count9
Package typeNot declared
ES module entryNot declared
Default entry./dist/bigint-crypto-utils-latest.node.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository stars38
Repository forks3

Install bigint-crypto-utils 2.5.2

npm install bigint-crypto-utils@2.5.2
pnpm add bigint-crypto-utils@2.5.2
yarn add bigint-crypto-utils@2.5.2

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.

Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Code-Review0/10 — Found 0/30 approved changesets -- score normalized to 0
Binary-Artifacts10/10 — no binaries found in the repo
SAST0/10 — no SAST tool detected
Maintained0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
Security-Policy0/10 — security policy file not detected
Fuzzing0/10 — project is not fuzzed
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches

Evidence and freshness