@tscircuit/math-utils
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
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.0.36 | 0 / 3 | |
| 0.0.35 | 0 / 3 | |
| 0.0.34 | 0 / 3 | |
| 0.0.33 | 0 / 3 | |
| 0.0.32 | 0 / 3 | |
| 0.0.31 | 0 / 3 | |
| 0.0.30 | 0 / 3 | |
| 0.0.29 | 0 / 3 | |
| 0.0.28 | 0 / 3 | |
| 0.0.27 | 0 / 3 | |
| 0.0.26 | 0 / 3 | |
| 0.0.25 | 0 / 3 | |
| 0.0.24 | 0 / 3 | |
| 0.0.23 | 0 / 3 | |
| 0.0.22 | 0 / 3 | |
| 0.0.21 | 0 / 3 | |
| 0.0.20 | 0 / 3 | |
| 0.0.19 | 0 / 3 | |
| 0.0.18 | 0 / 3 | |
| 0.0.17 | 0 / 3 |
v0.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.