← Home

d3-random

npm Repository Homepage

Generate random numbers from various distributions.

25
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mbostockrecifs

Keywords

d3d3-modulerandomrng

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): mbostock → recifs is the documented D3 org maintainer transition (2020). recifs has a strong track record (1238 approved packages). Legitimate handoff, not a compromise. ai
provenance missing-githead AI (provenance): Missing gitHead is consistent with the publish tooling change during the D3 org transition. No code changes vs prior version; not a meaningful risk signal for this package. ai

Versions (showing 25 of 25)

Version Deps Published
3.0.1 0 / 6
3.0.0 0 / 6
2.2.2 0 / 7
2.2.1 0 / 6
2.2.0 0 / 6
2.1.0 0 / 7
2.0.1 0 / 7
2.0.0 0 / 7
1.1.2 0 / 6
1.1.1 0 / 6
1.1.0 0 / 7
1.0.3 0 / 7
1.0.2 0 / 7
1.0.1 0 / 7
1.0.0 0 / 7
0.3.0 0 / 7
0.2.1 0 / 6
0.2.0 0 / 6
0.1.1 0 / 6
0.1.0 0 / 6
0.0.4 0 / 6
0.0.3 0 / 6
0.0.2 0 / 6
0.0.1 0 / 6
0.0.0 0 / 3

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.1

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: recifs.

HIGH Publisher changed: mbostock → recifs (on 2020-08-26) provenance

This version was published by a different npm account than previous versions on 2020-08-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.