@thi.ng/boids
n-dimensional boids simulation with modular behavior system
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): thi.ng/umbrella packages consistently publish without Sigstore provenance; stable false positive for this publisher. | ai | |
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Internal sibling dep from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/math | AI (dependencies): Internal sibling dep from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/vectors | AI (dependencies): Internal sibling dep from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/distance | AI (dependencies): Internal sibling dep from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/timestep | AI (dependencies): Internal sibling dep from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/geom-resample | AI (dependencies): Internal sibling dep from the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/geom-closest-point | AI (dependencies): Internal sibling dep from the same thi.ng/umbrella monorepo; stable false positive. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 1.1.57 | 8 / 3 | |
| 1.1.56 | 8 / 3 | |
| 1.1.55 | 8 / 3 | |
| 1.1.53 | 8 / 3 | |
| 1.1.52 | 8 / 3 | |
| 1.1.50 | 8 / 3 | |
| 1.1.49 | 8 / 3 | |
| 1.1.48 | 8 / 3 | |
| 1.1.47 | 8 / 3 | |
| 1.1.46 | 8 / 3 | |
| 1.1.45 | 8 / 3 | |
| 1.1.44 | 8 / 3 | |
| 1.1.43 | 8 / 3 | |
| 1.1.42 | 8 / 3 | |
| 1.1.41 | 8 / 3 | |
| 1.1.39 | 8 / 3 | |
| 1.1.38 | 8 / 3 | |
| 1.1.37 | 8 / 3 | |
| 1.1.36 | 8 / 3 | |
| 1.1.35 | 8 / 3 | |
| 1.1.34 | 8 / 3 | |
| 1.1.33 | 8 / 3 | |
| 1.1.32 | 8 / 3 | |
| 1.1.31 | 8 / 3 | |
| 1.1.30 | 8 / 3 | |
| 1.1.29 | 8 / 3 | |
| 1.1.25 | 8 / 3 | |
| 1.1.24 | 8 / 3 | |
| 1.1.23 | 8 / 3 | |
| 1.1.22 | 8 / 3 | |
| 1.1.20 | 8 / 3 | |
| 1.1.19 | 8 / 3 | |
| 1.1.18 | 8 / 3 | |
| 1.1.17 | 8 / 3 | |
| 1.1.16 | 8 / 3 | |
| 1.1.14 | 8 / 3 | |
| 1.1.13 | 8 / 3 | |
| 1.1.12 | 8 / 3 | |
| 1.1.11 | 8 / 3 | |
| 1.1.10 | 8 / 3 | |
| 1.1.9 | 8 / 3 | |
| 1.1.8 | 8 / 3 | |
| 1.1.7 | 8 / 3 | |
| 1.1.6 | 8 / 3 | |
| 1.1.5 | 8 / 3 | |
| 1.1.4 | 8 / 3 | |
| 1.1.3 | 8 / 3 | |
| 1.1.2 | 8 / 3 | |
| 1.1.1 | 8 / 3 | |
| 1.1.0 | 8 / 3 | |
| 1.0.78 | 8 / 3 |
v1.1.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.