@swapkit/toolboxes
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@meshsdk/core | AI (dependencies): Official Cardano Mesh SDK; matches new cardano toolbox export in this package. | ai | |
| dependencies | unvetted-dep:near-sdk-js | AI (dependencies): Legitimate NEAR blockchain SDK; expected dependency for a multi-chain toolbox. | ai | |
| dependencies | unvetted-dep:@psf/bitcoincashjs-lib | AI (dependencies): Bitcoin Cash library; consistent with UTXO toolbox functionality in this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding used for standard Bitcoin UTXO script construction; not obfuscation. | ai | |
| phantom-deps | phantom-dep:near-api-js | AI (phantom-deps): Bundled multi-chain toolbox; declared deps may not be directly imported in analyzed entry points. | ai | |
| phantom-deps | phantom-dep:@noble/hashes | AI (phantom-deps): Same bundled toolbox pattern; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@near-js/accounts | AI (dependencies): Official NEAR protocol SDK; expected dep for a multi-chain toolbox with a /near export. | ai | |
| dependencies | unvetted-dep:starknet | AI (dependencies): Legitimate StarkNet SDK; expected dep for a multi-chain toolbox with a /starknet export. | ai | |
| phantom-deps | phantom-dep:@mysten/bcs | AI (phantom-deps): @mysten/bcs is listed in both runtime and devDependencies; phantom-dep is a false positive here. | ai |
Versions (showing 51 of 70)
| Version | Deps | Published |
|---|---|---|
| 4.17.1 | 2 / 50 | |
| 4.17.0 | 2 / 50 | |
| 4.16.2 | 2 / 49 | |
| 4.16.1 | 2 / 49 | |
| 4.16.0 | 2 / 49 | |
| 4.15.15 | 2 / 49 | |
| 4.15.14 | 2 / 49 | |
| 4.15.13 | 2 / 49 | |
| 4.15.12 | 2 / 50 | |
| 4.15.11 | 2 / 50 | |
| 4.15.10 | 46 / 49 | |
| 4.15.9 | 46 / 49 | |
| 4.15.8 | 46 / 49 | |
| 4.15.7 | 46 / 49 | |
| 4.15.6 | 46 / 49 | |
| 4.15.5 | 46 / 49 | |
| 4.15.4 | 46 / 49 | |
| 4.15.3 | 46 / 49 | |
| 4.15.2 | 46 / 49 | |
| 4.15.1 | 46 / 49 | |
| 4.15.0 | 46 / 49 | |
| 4.14.5 | 46 / 49 | |
| 4.14.4 | 46 / 49 | |
| 4.14.3 | 46 / 49 | |
| 4.14.2 | 46 / 49 | |
| 4.14.1 | 46 / 49 | |
| 4.14.0 | 46 / 49 | |
| 4.13.3 | 46 / 49 | |
| 4.13.2 | 46 / 49 | |
| 4.13.1 | 46 / 49 | |
| 4.3.10 | 48 / 54 | |
| 4.3.7 | 48 / 54 | |
| 4.3.4 | 48 / 54 | |
| 4.3.3 | 48 / 54 | |
| 4.3.2 | 48 / 54 | |
| 4.1.13 | 42 / 49 | |
| 4.1.12 | 42 / 49 | |
| 4.1.11 | 42 / 49 | |
| 4.1.8 | 42 / 49 | |
| 4.1.4 | 42 / 49 | |
| 4.1.3 | 42 / 49 | |
| 4.1.0 | 42 / 49 | |
| 4.0.27 | 37 / 42 | |
| 4.0.26 | 37 / 42 | |
| 4.0.25 | 37 / 42 | |
| 4.0.24 | 37 / 42 | |
| 4.0.23 | 37 / 42 | |
| 4.0.22 | 37 / 42 | |
| 4.0.21 | 37 / 42 | |
| 4.0.20 | 37 / 42 | |
| 4.0.19 | 37 / 42 |
v4.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.