@swapkit/wallet-extensions
SwapKit - Wallet Extension
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@near-js/accounts | AI (dependencies): Legitimate NEAR Protocol SDK; expected dependency for a multi-chain wallet extension. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes PSBT from wallet extension response — standard Bitcoin transaction handling, not obfuscation. | ai | |
| phantom-deps | phantom-dep:cosmjs-types | AI (phantom-deps): Declared in both runtime and devDependencies; used transitively via cosmjs ecosystem. | ai | |
| phantom-deps | phantom-dep:@cosmjs/stargate | AI (phantom-deps): Declared in both runtime and devDependencies; used via config/type re-exports. | ai | |
| phantom-deps | phantom-dep:@aptos-labs/ts-sdk | AI (phantom-deps): Declared in both runtime and devDependencies; used via config/type re-exports. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 4.5.17 | 18 / 14 | |
| 4.5.16 | 18 / 14 | |
| 4.5.15 | 18 / 14 | |
| 4.5.14 | 18 / 14 | |
| 4.5.13 | 18 / 14 | |
| 4.5.12 | 18 / 14 | |
| 4.5.11 | 18 / 14 | |
| 4.5.10 | 18 / 14 | |
| 4.5.9 | 18 / 14 | |
| 4.5.8 | 18 / 14 | |
| 4.5.7 | 18 / 14 | |
| 4.5.6 | 18 / 14 | |
| 4.5.5 | 18 / 14 | |
| 4.5.4 | 18 / 14 | |
| 4.5.3 | 18 / 14 | |
| 4.5.2 | 18 / 14 | |
| 4.5.1 | 18 / 14 | |
| 4.5.0 | 18 / 14 | |
| 4.4.3 | 17 / 14 | |
| 4.4.2 | 17 / 14 | |
| 4.4.1 | 17 / 14 | |
| 4.4.0 | 17 / 14 | |
| 4.1.11 | 11 / 8 | |
| 4.1.10 | 11 / 8 | |
| 4.1.9 | 11 / 8 | |
| 4.1.8 | 11 / 8 | |
| 4.1.7 | 11 / 8 | |
| 4.1.6 | 11 / 8 | |
| 4.1.5 | 11 / 8 | |
| 4.1.4 | 11 / 8 | |
| 4.1.3 | 11 / 8 | |
| 4.1.2 | 11 / 8 |
v4.5.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.