@thi.ng/geom-splines
nD cubic & quadratic curve analysis, conversion, interpolation, splitting
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 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 for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/math | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/vectors | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/geom-arc | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@thi.ng/geom-resample | AI (dependencies): Sibling package in thi.ng/umbrella monorepo; stable false positive for this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 2.3.92 | 6 / 3 | |
| 2.3.91 | 6 / 3 | |
| 2.3.90 | 6 / 3 | |
| 2.3.88 | 6 / 3 | |
| 2.3.87 | 6 / 3 | |
| 2.3.85 | 6 / 3 | |
| 2.3.84 | 6 / 3 | |
| 2.3.83 | 6 / 3 | |
| 2.3.82 | 6 / 3 | |
| 2.3.81 | 6 / 3 | |
| 2.3.80 | 6 / 3 | |
| 2.3.79 | 6 / 3 | |
| 2.3.78 | 6 / 3 | |
| 2.3.77 | 6 / 3 | |
| 2.3.76 | 6 / 3 | |
| 2.3.75 | 6 / 3 | |
| 2.3.74 | 6 / 3 | |
| 2.3.73 | 6 / 3 | |
| 2.3.72 | 6 / 3 | |
| 2.3.71 | 6 / 3 | |
| 2.3.70 | 6 / 3 | |
| 2.3.69 | 6 / 3 | |
| 2.3.68 | 6 / 3 | |
| 2.3.67 | 6 / 3 | |
| 2.3.66 | 6 / 3 | |
| 2.3.62 | 6 / 3 | |
| 2.3.61 | 6 / 3 | |
| 2.3.60 | 6 / 3 | |
| 2.3.59 | 6 / 3 | |
| 2.3.58 | 6 / 3 | |
| 2.3.57 | 6 / 3 | |
| 2.3.56 | 6 / 3 | |
| 2.3.55 | 6 / 3 | |
| 2.3.54 | 6 / 3 | |
| 2.3.53 | 6 / 3 | |
| 2.3.51 | 6 / 3 | |
| 2.3.50 | 6 / 3 | |
| 2.3.49 | 6 / 3 | |
| 2.3.48 | 6 / 3 | |
| 2.3.47 | 6 / 3 | |
| 2.3.46 | 6 / 3 | |
| 2.3.45 | 6 / 3 | |
| 2.3.44 | 6 / 3 | |
| 2.3.43 | 6 / 3 |
v2.3.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.91
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.90
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.88
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.87
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.85
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.76
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.71
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.67
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.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.