@tcswap/wallet-hardware
USwap - Wallet Hardware
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Standard crypto tx serialization (XRP txBlob base64→hex); stable pattern for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Standard crypto pubkey encoding (hex→base64); stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/wallet-api-client | AI (phantom-deps): Declared in both deps and devDeps; likely used transitively or in config. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 4.2.21 | 25 / 22 | |
| 4.2.19 | 25 / 22 | |
| 4.2.18 | 25 / 22 | |
| 4.2.17 | 25 / 22 |
v4.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.