@thi.ng/random
Pseudo-random number generators w/ unified API, distributions, weighted choices, ID generation
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): thi.ng/umbrella monorepo does not publish with Sigstore provenance; stable pattern across all its packages. | ai | |
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): First-party sibling dep within the thi.ng/umbrella monorepo; stable across all versions. | ai |
Versions (showing 55 of 55)
| Version | Deps | Published |
|---|---|---|
| 4.1.53 | 2 / 3 | |
| 4.1.52 | 2 / 3 | |
| 4.1.51 | 2 / 3 | |
| 4.1.50 | 2 / 3 | |
| 4.1.48 | 2 / 3 | |
| 4.1.47 | 2 / 3 | |
| 4.1.45 | 2 / 3 | |
| 4.1.44 | 2 / 3 | |
| 4.1.43 | 2 / 3 | |
| 4.1.42 | 2 / 3 | |
| 4.1.41 | 2 / 3 | |
| 4.1.40 | 2 / 3 | |
| 4.1.39 | 2 / 3 | |
| 4.1.38 | 2 / 3 | |
| 4.1.37 | 2 / 3 | |
| 4.1.36 | 2 / 3 | |
| 4.1.35 | 2 / 3 | |
| 4.1.34 | 2 / 3 | |
| 4.1.33 | 2 / 3 | |
| 4.1.32 | 2 / 3 | |
| 4.1.31 | 2 / 3 | |
| 4.1.30 | 2 / 3 | |
| 4.1.27 | 2 / 3 | |
| 4.1.26 | 2 / 3 | |
| 4.1.25 | 2 / 3 | |
| 4.1.24 | 2 / 3 | |
| 4.1.23 | 2 / 3 | |
| 4.1.22 | 2 / 3 | |
| 4.1.21 | 2 / 3 | |
| 4.1.20 | 2 / 3 | |
| 4.1.19 | 2 / 3 | |
| 4.1.18 | 2 / 3 | |
| 4.1.17 | 2 / 3 | |
| 4.1.16 | 2 / 3 | |
| 4.1.15 | 2 / 3 | |
| 4.1.14 | 2 / 3 | |
| 4.1.13 | 2 / 3 | |
| 4.1.12 | 2 / 3 | |
| 4.1.11 | 2 / 3 | |
| 4.1.10 | 2 / 3 | |
| 4.1.9 | 2 / 3 | |
| 4.1.8 | 2 / 4 | |
| 4.1.7 | 2 / 4 | |
| 4.1.6 | 2 / 4 | |
| 4.1.5 | 2 / 4 | |
| 4.1.4 | 2 / 4 | |
| 4.1.3 | 2 / 4 | |
| 4.1.2 | 2 / 4 | |
| 4.1.1 | 2 / 4 | |
| 4.1.0 | 2 / 4 | |
| 4.0.4 | 2 / 4 | |
| 4.0.3 | 2 / 4 | |
| 4.0.2 | 2 / 4 | |
| 4.0.1 | 2 / 4 | |
| 4.0.0 | 2 / 4 |
v4.1.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.