@thi.ng/geom
Functional, polymorphic API for 2D geometry types & SVG generation
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped geometry library; Levenshtein match to 'glob' is spurious. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped geometry library; Levenshtein match to 'got' is spurious. | ai |
Versions (showing 51 of 60)
| Version | Deps | Published |
|---|---|---|
| 8.3.34 | 27 / 3 | |
| 8.3.33 | 27 / 3 | |
| 8.3.32 | 27 / 3 | |
| 8.3.30 | 27 / 3 | |
| 8.3.29 | 27 / 3 | |
| 8.3.27 | 27 / 3 | |
| 8.3.26 | 27 / 3 | |
| 8.3.25 | 27 / 3 | |
| 8.3.24 | 27 / 3 | |
| 8.3.23 | 27 / 3 | |
| 8.3.22 | 27 / 3 | |
| 8.3.21 | 27 / 3 | |
| 8.3.20 | 27 / 3 | |
| 8.3.19 | 27 / 3 | |
| 8.3.18 | 27 / 3 | |
| 8.3.17 | 27 / 3 | |
| 8.3.15 | 27 / 3 | |
| 8.3.14 | 27 / 3 | |
| 8.3.13 | 27 / 3 | |
| 8.3.12 | 27 / 3 | |
| 8.3.11 | 27 / 3 | |
| 8.3.10 | 27 / 3 | |
| 8.3.9 | 27 / 3 | |
| 8.3.8 | 27 / 3 | |
| 8.3.7 | 27 / 3 | |
| 8.3.6 | 27 / 3 | |
| 8.3.5 | 27 / 3 | |
| 8.3.4 | 27 / 3 | |
| 8.3.3 | 27 / 3 | |
| 8.2.14 | 27 / 3 | |
| 8.2.13 | 27 / 3 | |
| 8.2.12 | 27 / 3 | |
| 8.2.11 | 27 / 3 | |
| 8.2.10 | 27 / 3 | |
| 8.2.9 | 27 / 3 | |
| 8.2.8 | 27 / 3 | |
| 8.2.7 | 27 / 3 | |
| 8.2.6 | 27 / 3 | |
| 8.2.5 | 27 / 3 | |
| 8.2.4 | 27 / 3 | |
| 8.2.3 | 27 / 3 | |
| 8.2.2 | 27 / 3 | |
| 8.2.0 | 27 / 3 | |
| 8.1.57 | 27 / 3 | |
| 8.1.56 | 27 / 3 | |
| 8.1.55 | 27 / 3 | |
| 8.1.54 | 27 / 3 | |
| 8.1.53 | 27 / 3 | |
| 8.1.52 | 27 / 3 | |
| 8.1.51 | 27 / 3 | |
| 8.1.50 | 27 / 3 |
v8.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.