@thi.ng/arcball
3D arcball controller for intuitive click & drag gesture-based camera view rotations. Quaternion-based.
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 monorepo does not use Sigstore attestation; consistent across all its packages. | ai | |
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; not an independent risk. | ai | |
| dependencies | unvetted-dep:@thi.ng/vectors | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; not an independent risk. | ai | |
| dependencies | unvetted-dep:@thi.ng/matrices | AI (dependencies): Sibling package from the same thi.ng/umbrella monorepo; not an independent risk. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.1.23 | 3 / 3 | |
| 1.1.22 | 3 / 3 | |
| 1.1.21 | 3 / 3 | |
| 1.1.19 | 3 / 3 | |
| 1.1.18 | 3 / 3 | |
| 1.1.16 | 3 / 3 | |
| 1.1.15 | 3 / 3 | |
| 1.1.14 | 3 / 3 | |
| 1.1.13 | 3 / 3 | |
| 1.1.12 | 3 / 3 | |
| 1.1.11 | 3 / 3 | |
| 1.1.10 | 3 / 3 | |
| 1.1.9 | 3 / 3 | |
| 1.1.8 | 3 / 3 | |
| 1.1.7 | 3 / 3 | |
| 1.1.6 | 3 / 3 | |
| 1.1.5 | 3 / 3 | |
| 1.1.4 | 3 / 3 | |
| 1.1.3 | 3 / 3 | |
| 1.1.2 | 3 / 3 | |
| 1.1.1 | 3 / 3 |
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.21
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.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.