@swapkit/wallet-hardware
SwapKit - Wallet Hardware
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @scure/bip32 is a well-audited cryptographic library appropriate for a hardware wallet package. | ai | |
| phantom-deps | phantom-dep:@cosmjs/proto-signing | AI (phantom-deps): Config-only reference; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:cosmjs-types | AI (phantom-deps): Config-only reference; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@keepkey/keepkey-sdk | AI (dependencies): Expected dependency for KeepKey hardware wallet support; stable for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decoding XRP tx blob from base64 to hex is standard hardware wallet signing; not obfuscation. | ai | |
| phantom-deps | phantom-dep:@ledgerhq/wallet-api-client | AI (phantom-deps): @ledgerhq/wallet-api-client is declared as a runtime dep and likely used indirectly; phantom-dep heuristic false positive for this package. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Converting Ledger public key from hex to base64 is standard crypto key encoding; not malicious. | ai |
Versions (showing 93 of 93)
| Version | Deps | Published |
|---|---|---|
| 4.9.29 | 32 / 28 | |
| 4.9.27 | 32 / 28 | |
| 4.9.26 | 32 / 28 | |
| 4.9.25 | 32 / 28 | |
| 4.9.24 | 32 / 28 | |
| 4.9.23 | 32 / 28 | |
| 4.9.22 | 32 / 28 | |
| 4.9.21 | 32 / 28 | |
| 4.9.20 | 32 / 28 | |
| 4.9.19 | 32 / 28 | |
| 4.9.18 | 32 / 28 | |
| 4.9.17 | 32 / 28 | |
| 4.9.16 | 32 / 28 | |
| 4.9.15 | 32 / 28 | |
| 4.9.14 | 32 / 28 | |
| 4.9.13 | 32 / 28 | |
| 4.9.12 | 32 / 28 | |
| 4.9.11 | 32 / 28 | |
| 4.9.10 | 32 / 28 | |
| 4.9.9 | 32 / 28 | |
| 4.9.8 | 32 / 28 | |
| 4.9.7 | 32 / 28 | |
| 4.9.6 | 31 / 27 | |
| 4.9.5 | 31 / 27 | |
| 4.9.4 | 31 / 27 | |
| 4.9.3 | 31 / 27 | |
| 4.9.2 | 31 / 27 | |
| 4.9.1 | 31 / 27 | |
| 4.9.0 | 31 / 27 | |
| 4.8.4 | 31 / 27 | |
| 4.8.3 | 31 / 27 | |
| 4.8.2 | 31 / 27 | |
| 4.8.1 | 31 / 27 | |
| 4.8.0 | 30 / 26 | |
| 4.7.0 | 30 / 26 | |
| 4.6.3 | 29 / 26 | |
| 4.6.2 | 29 / 26 | |
| 4.6.1 | 29 / 26 | |
| 4.6.0 | 29 / 26 | |
| 4.2.11 | 25 / 22 | |
| 4.2.10 | 25 / 22 | |
| 4.2.9 | 25 / 22 | |
| 4.2.8 | 25 / 22 | |
| 4.2.7 | 25 / 22 | |
| 4.2.6 | 25 / 22 | |
| 4.2.5 | 25 / 22 | |
| 4.2.4 | 25 / 22 | |
| 4.2.3 | 25 / 22 | |
| 4.2.2 | 25 / 22 | |
| 4.1.42 | 17 / 15 | |
| 4.1.41 | 17 / 15 | |
| 4.1.40 | 17 / 15 | |
| 4.1.39 | 17 / 15 | |
| 4.1.38 | 17 / 15 | |
| 4.1.37 | 17 / 15 | |
| 4.1.36 | 17 / 15 | |
| 4.1.35 | 17 / 15 | |
| 4.1.34 | 17 / 15 | |
| 4.1.33 | 17 / 15 | |
| 4.1.32 | 17 / 15 | |
| 4.1.31 | 16 / 14 | |
| 4.1.30 | 16 / 14 | |
| 4.1.29 | 16 / 14 | |
| 4.1.28 | 16 / 14 | |
| 4.1.27 | 16 / 14 | |
| 4.1.26 | 16 / 14 | |
| 4.1.25 | 16 / 14 | |
| 4.1.24 | 16 / 14 | |
| 4.1.23 | 16 / 14 | |
| 4.1.22 | 16 / 14 | |
| 4.1.21 | 16 / 14 | |
| 4.1.20 | 16 / 14 | |
| 4.1.19 | 16 / 14 | |
| 4.1.18 | 16 / 14 | |
| 4.1.17 | 16 / 14 | |
| 4.1.16 | 16 / 14 | |
| 4.1.15 | 16 / 14 | |
| 4.1.14 | 16 / 14 | |
| 4.1.13 | 16 / 14 | |
| 4.1.12 | 16 / 14 | |
| 4.1.11 | 16 / 14 | |
| 4.1.10 | 16 / 14 | |
| 4.1.9 | 16 / 14 | |
| 4.1.8 | 16 / 14 | |
| 4.1.7 | 16 / 14 | |
| 4.1.6 | 16 / 14 | |
| 4.1.5 | 16 / 14 | |
| 4.1.4 | 16 / 14 | |
| 4.1.3 | 16 / 14 | |
| 4.1.2 | 16 / 14 | |
| 4.1.1 | 16 / 14 | |
| 4.1.0 | 16 / 14 | |
| 4.0.0 | 16 / 14 |
v4.9.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.8.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.8.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.8.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.9
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.