@thi.ng/geom-tessellate
2D/3D convex polygon tessellators
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 provenance; consistent across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/math | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/morton | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/vectors | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/geom-isec | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/geom-accel | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/transducers | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/geom-poly-utils | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive. | ai |
Versions (showing 53 of 53)
| Version | Deps | Published |
|---|---|---|
| 3.0.102 | 9 / 3 | |
| 3.0.101 | 9 / 3 | |
| 3.0.100 | 9 / 3 | |
| 3.0.98 | 9 / 3 | |
| 3.0.97 | 9 / 3 | |
| 3.0.95 | 9 / 3 | |
| 3.0.94 | 9 / 3 | |
| 3.0.93 | 9 / 3 | |
| 3.0.92 | 9 / 3 | |
| 3.0.91 | 9 / 3 | |
| 3.0.90 | 9 / 3 | |
| 3.0.89 | 9 / 3 | |
| 3.0.88 | 9 / 3 | |
| 3.0.87 | 9 / 3 | |
| 3.0.86 | 9 / 3 | |
| 3.0.85 | 9 / 3 | |
| 3.0.83 | 9 / 3 | |
| 3.0.82 | 9 / 3 | |
| 3.0.81 | 9 / 3 | |
| 3.0.80 | 9 / 3 | |
| 3.0.79 | 9 / 3 | |
| 3.0.78 | 9 / 3 | |
| 3.0.77 | 9 / 3 | |
| 3.0.76 | 9 / 3 | |
| 3.0.75 | 9 / 3 | |
| 3.0.74 | 9 / 3 | |
| 3.0.73 | 9 / 3 | |
| 3.0.69 | 9 / 3 | |
| 3.0.68 | 9 / 3 | |
| 3.0.67 | 9 / 3 | |
| 3.0.66 | 9 / 3 | |
| 3.0.65 | 9 / 3 | |
| 3.0.64 | 9 / 3 | |
| 3.0.63 | 9 / 3 | |
| 3.0.62 | 9 / 3 | |
| 3.0.61 | 9 / 3 | |
| 3.0.60 | 9 / 3 | |
| 3.0.59 | 9 / 3 | |
| 3.0.57 | 9 / 3 | |
| 3.0.56 | 9 / 3 | |
| 3.0.55 | 9 / 3 | |
| 3.0.54 | 9 / 3 | |
| 3.0.53 | 9 / 3 | |
| 3.0.52 | 9 / 3 | |
| 3.0.51 | 9 / 3 | |
| 3.0.50 | 9 / 3 | |
| 3.0.49 | 9 / 3 | |
| 3.0.48 | 9 / 3 | |
| 3.0.47 | 9 / 3 | |
| 3.0.46 | 9 / 3 | |
| 3.0.45 | 9 / 3 | |
| 3.0.44 | 9 / 3 | |
| 3.0.43 | 9 / 3 |
v3.0.102
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.101
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.100
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.98
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.97
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.95
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.94
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.93
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.89
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.86
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.85
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.