Back to Explore

dubzzz/pure-rand

GitHub
4 updates · last 90 days1 watchersOpen source

Last release: 2 months ago

Pure-rand is a set of fast pseudorandom number generators and uniform distributions for JavaScript or TypeScript. It provides deterministic PRNGs with an emphasis on “pure” usage, where calling the generator returns the next RNG state without altering the existing one, which is useful for reproducible randomness and functional-style simulations.

Project status

  • Actively maintained: The repo has a recent upstream push (2026-06-07), and versioned updates are being published in 2026 (v8.2.0, v8.3.0, v8.4.0).
  • Updates cadence (approx.): Based on the provided tags, updates appear to be frequent, with v8.2.0 on 2026-03-16, v8.3.0 on 2026-03-19, and v8.4.0 on 2026-03-27 (roughly every few days to about 1.5 weeks during that period).

AI summary generated Today

AI-generated from public sources. May be inaccurate. Report

Recent updates

  • v8.4.0

    2 months ago

    No publisher release notes were provided for v8.4.0. From the repo changes, this release focuses on changing how Mersenne Twister jump coefficients are stored/computed, alongside CI and tooling workflow updates (node version, action versions, and skipping the bench job on non-PR events).

    Features
  • v8.3.0

    2 months ago

    No release notes were provided for v8.3.0. The code diff shows several generator behavior and implementation changes, including adding jump support for the Mersenne Twister generator and optimizing congruential32’s 32-bit multiplication.

  • v8.2.0

    2 months ago

    Release v8.2.0 was published on 2026-03-16, but the publisher provided no release notes. Without documented changes, developers should review the tag diff, changelog in the repository (if any), and run integration tests before upgrading.

  • v8.1.0

    2 months ago

    This release adds two new uniform floating point distributions, `uniformFloat32` and `uniformFloat64`, and updates documentation and benchmarks/tests to cover them. It also bumps several dev dependencies and adjusts CI workflows related to pnpm setup and the Claude review bot configuration.

    Features
  • v8.0.0

    3 months ago

    v8.0.0 has no release notes provided. The code diff shows a major internal refactor around RNG and distribution generation, plus repository-wide tooling changes (yarn to pnpm, updated CI workflows). Several API-level changes appear to affect how consumers use RNGs and distributions, but none are documented.

  • v7.0.1

    2/7/2025

    v7.0.1 contains CI and build tooling updates, plus a packaging fix to the package.json exports map. The GitHub release notes were not provided, so the change details visible in the repo (exports/build tooling, Yarn toolchain, and dev dependency bumps) are not documented there.

  • v7.0.0

    2/6/2025

    No release notes were provided in the GitHub release metadata for v7.0.0. The code diff shows a v6.1.0 to v7.0.0 refactor that changes public TypeScript contracts (notably `RandomGenerator.getState`) and alters several module export shapes and import paths.

  • v6.1.0

    3/20/2024

    This release (v6.1.0) introduces the ability to access and clone the internal state of the library PRNG generators (getState, and fromState constructors for multiple generators). The diff also includes CI/tooling updates, including an upgrade of the package manager tooling (Yarn 3 to Yarn 4) and newer GitHub Actions dependencies. No publisher release notes were provided for this version.

    Features
  • v6.0.4

    9/27/2023

    v6.0.4 does not include any release-note content in the provided release notes. The diff indicates the main changes are build/typing post-processing (for Node ESM native typings), plus CI workflow updates and dev dependency bumps.

  • v6.0.3

    9/4/2023

    Release v6.0.3 was published on 2023-09-04, but the publisher did not provide any release notes. Because no change log or notes were included, there is insufficient information to identify new features, bug fixes, breaking changes, or security updates from the release text alone. Developers should review the code diff between v6.0.2 and v6.0.3 to assess upgrade impact.