@ethsign/utils-tokentable
Contract utils from TokenTable
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@coral-xyz/anchor | AI (phantom-deps): @coral-xyz/anchor is a declared runtime dependency for Solana support; phantom-dep heuristic fires but it's legitimately used. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.11.11 | 7 / 1 | |
| 0.11.10 | 7 / 1 | |
| 0.11.9 | 7 / 1 | |
| 0.10.4 | 7 / 1 | |
| 0.10.3 | 7 / 1 | |
| 0.10.2 | 7 / 1 | |
| 0.10.0 | 7 / 1 | |
| 0.9.5 | 7 / 1 | |
| 0.9.4 | 7 / 1 |
v0.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.