@thi.ng/tsne
Highly configurable t-SNE implementation for arbitrary dimensions
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): Internal thi.ng umbrella monorepo dep; same publisher, stable pattern. | ai | |
| dependencies | unvetted-dep:@thi.ng/math | AI (dependencies): Internal thi.ng umbrella monorepo dep; same publisher, stable pattern. | ai | |
| dependencies | unvetted-dep:@thi.ng/random | AI (dependencies): Internal thi.ng umbrella monorepo dep; same publisher, stable pattern. | ai | |
| dependencies | unvetted-dep:@thi.ng/vectors | AI (dependencies): Internal thi.ng umbrella monorepo dep; same publisher, stable pattern. | ai | |
| dependencies | unvetted-dep:@thi.ng/transducers | AI (dependencies): Internal thi.ng umbrella monorepo dep; same publisher, stable pattern. | ai |
Versions (showing 51 of 54)
| Version | Deps | Published |
|---|---|---|
| 0.1.71 | 5 / 3 | |
| 0.1.70 | 5 / 3 | |
| 0.1.69 | 5 / 3 | |
| 0.1.67 | 5 / 3 | |
| 0.1.66 | 5 / 3 | |
| 0.1.64 | 5 / 3 | |
| 0.1.63 | 5 / 3 | |
| 0.1.62 | 5 / 3 | |
| 0.1.61 | 5 / 3 | |
| 0.1.60 | 5 / 3 | |
| 0.1.59 | 5 / 3 | |
| 0.1.58 | 5 / 3 | |
| 0.1.57 | 5 / 3 | |
| 0.1.56 | 5 / 3 | |
| 0.1.55 | 5 / 3 | |
| 0.1.54 | 5 / 3 | |
| 0.1.52 | 5 / 3 | |
| 0.1.51 | 5 / 3 | |
| 0.1.50 | 5 / 3 | |
| 0.1.49 | 5 / 3 | |
| 0.1.48 | 5 / 3 | |
| 0.1.47 | 5 / 3 | |
| 0.1.46 | 5 / 3 | |
| 0.1.45 | 5 / 3 | |
| 0.1.44 | 5 / 3 | |
| 0.1.43 | 5 / 3 | |
| 0.1.42 | 5 / 3 | |
| 0.1.38 | 5 / 3 | |
| 0.1.37 | 5 / 3 | |
| 0.1.36 | 5 / 3 | |
| 0.1.35 | 5 / 3 | |
| 0.1.34 | 5 / 3 | |
| 0.1.33 | 5 / 3 | |
| 0.1.32 | 5 / 3 | |
| 0.1.31 | 5 / 3 | |
| 0.1.30 | 5 / 3 | |
| 0.1.29 | 5 / 3 | |
| 0.1.28 | 5 / 3 | |
| 0.1.26 | 5 / 3 | |
| 0.1.25 | 5 / 3 | |
| 0.1.24 | 5 / 3 | |
| 0.1.23 | 5 / 3 | |
| 0.1.22 | 5 / 3 | |
| 0.1.21 | 5 / 3 | |
| 0.1.20 | 5 / 3 | |
| 0.1.19 | 5 / 3 | |
| 0.1.18 | 5 / 3 | |
| 0.1.17 | 5 / 3 | |
| 0.1.16 | 5 / 3 | |
| 0.1.15 | 5 / 3 | |
| 0.1.14 | 5 / 3 |
v0.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.60
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.