@thi.ng/poisson
nD Stratified grid and Poisson-disc sampling w/ support for spatial density functions and custom PRNGs
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/random | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/vectors | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/geom-accel | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive for this package. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 3.2.95 | 5 / 3 | |
| 3.2.94 | 5 / 3 | |
| 3.2.93 | 5 / 3 | |
| 3.2.91 | 5 / 3 | |
| 3.2.90 | 5 / 3 | |
| 3.2.88 | 5 / 3 | |
| 3.2.87 | 5 / 3 | |
| 3.2.86 | 5 / 3 | |
| 3.2.85 | 5 / 3 | |
| 3.2.84 | 5 / 3 | |
| 3.2.83 | 5 / 3 | |
| 3.2.82 | 5 / 3 | |
| 3.2.81 | 5 / 3 | |
| 3.2.80 | 5 / 3 | |
| 3.2.79 | 5 / 3 | |
| 3.2.78 | 5 / 3 | |
| 3.2.76 | 5 / 3 | |
| 3.2.75 | 5 / 3 | |
| 3.2.74 | 5 / 3 | |
| 3.2.73 | 5 / 3 | |
| 3.2.72 | 5 / 3 | |
| 3.2.71 | 5 / 3 | |
| 3.2.70 | 5 / 3 | |
| 3.2.69 | 5 / 3 | |
| 3.2.68 | 5 / 3 | |
| 3.2.67 | 5 / 3 | |
| 3.2.66 | 5 / 3 | |
| 3.2.62 | 5 / 3 | |
| 3.2.61 | 5 / 3 | |
| 3.2.60 | 5 / 3 | |
| 3.2.59 | 5 / 3 | |
| 3.2.58 | 5 / 3 | |
| 3.2.56 | 5 / 3 | |
| 3.2.55 | 5 / 3 | |
| 3.2.54 | 5 / 3 | |
| 3.2.53 | 5 / 3 | |
| 3.2.52 | 5 / 3 | |
| 3.2.50 | 5 / 3 | |
| 3.2.49 | 5 / 3 | |
| 3.2.48 | 5 / 3 | |
| 3.2.47 | 5 / 3 | |
| 3.2.46 | 5 / 3 | |
| 3.2.45 | 5 / 3 | |
| 3.2.44 | 5 / 3 | |
| 3.2.43 | 5 / 3 | |
| 3.2.42 | 5 / 3 | |
| 3.2.41 | 5 / 3 | |
| 3.2.40 | 5 / 3 | |
| 3.2.39 | 5 / 3 | |
| 3.2.38 | 5 / 3 | |
| 3.2.37 | 5 / 3 |
v3.2.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.88
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.87
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.79
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.76
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.75
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.72
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.69
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.