@thi.ng/math
Assorted common math functions & utilities
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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 consistently publishes without Sigstore provenance; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Same thi.ng/umbrella monorepo; sibling dep from the same trusted publisher. | ai |
Versions (showing 100 of 145)
| Version | Deps | Published |
|---|---|---|
| 5.15.16 | 1 / 3 | |
| 5.15.15 | 1 / 3 | |
| 5.15.14 | 1 / 3 | |
| 5.15.13 | 1 / 3 | |
| 5.15.11 | 1 / 3 | |
| 5.15.10 | 1 / 3 | |
| 5.15.9 | 1 / 3 | |
| 5.15.8 | 1 / 3 | |
| 5.15.7 | 1 / 3 | |
| 5.15.6 | 1 / 3 | |
| 5.15.5 | 1 / 3 | |
| 5.15.4 | 1 / 3 | |
| 5.15.3 | 1 / 3 | |
| 5.15.2 | 1 / 3 | |
| 5.15.1 | 1 / 3 | |
| 5.15.0 | 1 / 3 | |
| 5.14.0 | 1 / 3 | |
| 5.13.6 | 1 / 3 | |
| 5.13.5 | 1 / 3 | |
| 5.13.4 | 1 / 3 | |
| 5.13.3 | 1 / 3 | |
| 5.12.0 | 1 / 3 | |
| 5.11.35 | 1 / 3 | |
| 5.11.34 | 1 / 3 | |
| 5.11.33 | 1 / 3 | |
| 5.11.32 | 1 / 3 | |
| 5.11.31 | 1 / 3 | |
| 5.11.30 | 1 / 3 | |
| 5.11.29 | 1 / 3 | |
| 5.11.28 | 1 / 3 | |
| 5.11.27 | 1 / 3 | |
| 5.11.26 | 1 / 3 | |
| 5.11.25 | 1 / 3 | |
| 5.11.24 | 1 / 3 | |
| 5.11.23 | 1 / 3 | |
| 5.11.22 | 1 / 3 | |
| 5.11.21 | 1 / 3 | |
| 5.11.20 | 1 / 3 | |
| 5.11.19 | 1 / 3 | |
| 5.11.18 | 1 / 3 | |
| 5.11.17 | 1 / 4 | |
| 5.11.16 | 1 / 4 | |
| 5.11.15 | 1 / 4 | |
| 5.11.14 | 1 / 4 | |
| 5.11.13 | 1 / 4 | |
| 5.11.12 | 1 / 4 | |
| 5.11.11 | 1 / 4 | |
| 5.11.10 | 1 / 4 | |
| 5.11.9 | 1 / 4 | |
| 5.11.8 | 1 / 4 | |
| 5.11.7 | 1 / 4 | |
| 5.11.6 | 1 / 4 | |
| 5.11.5 | 1 / 4 | |
| 5.11.4 | 1 / 4 | |
| 5.11.3 | 1 / 4 | |
| 5.11.2 | 1 / 4 | |
| 5.11.1 | 1 / 4 | |
| 5.11.0 | 1 / 4 | |
| 5.10.13 | 1 / 4 | |
| 5.10.12 | 1 / 4 | |
| 5.10.11 | 1 / 5 | |
| 5.10.10 | 1 / 5 | |
| 5.10.9 | 1 / 5 | |
| 5.10.8 | 1 / 5 | |
| 5.10.7 | 1 / 5 | |
| 5.10.6 | 1 / 5 | |
| 5.10.5 | 1 / 5 | |
| 5.10.4 | 1 / 5 | |
| 5.10.3 | 1 / 5 | |
| 5.10.2 | 1 / 5 | |
| 5.10.1 | 1 / 5 | |
| 5.10.0 | 1 / 5 | |
| 5.9.1 | 1 / 5 | |
| 5.9.0 | 1 / 5 | |
| 5.8.4 | 1 / 5 | |
| 5.8.3 | 1 / 5 | |
| 5.8.2 | 1 / 5 | |
| 5.8.1 | 1 / 5 | |
| 5.8.0 | 1 / 5 | |
| 5.7.12 | 1 / 5 | |
| 5.7.11 | 1 / 5 | |
| 5.7.10 | 1 / 5 | |
| 5.7.9 | 1 / 5 | |
| 5.7.8 | 1 / 6 | |
| 5.7.7 | 1 / 6 | |
| 5.7.6 | 1 / 5 | |
| 5.7.5 | 1 / 6 | |
| 5.7.4 | 1 / 6 | |
| 5.7.3 | 1 / 6 | |
| 5.7.2 | 1 / 6 | |
| 5.7.1 | 1 / 6 | |
| 5.7.0 | 1 / 6 | |
| 5.6.3 | 1 / 6 | |
| 5.6.2 | 1 / 6 | |
| 5.6.1 | 1 / 6 | |
| 5.6.0 | 1 / 6 | |
| 5.5.5 | 1 / 6 | |
| 5.5.4 | 1 / 6 | |
| 5.5.3 | 1 / 6 | |
| 5.5.2 | 1 / 6 |
v5.15.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.