@swapkit/sdk
SwapKit - SDK
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:cosmjs-types | AI (phantom-deps): Declared as a transitive type dependency re-exported by the SDK bundle; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@stricahq/typhonjs | AI (phantom-deps): Cardano toolbox dependency declared at SDK level for bundling; stable false positive. | ai | |
| phantom-deps | phantom-dep:@swapkit/wallet-keystore | AI (phantom-deps): Same-org monorepo package re-exported via wallets entry; stable false positive. | ai |
Versions (showing 93 of 93)
| Version | Deps | Published |
|---|---|---|
| 4.6.30 | 10 / 0 | |
| 4.6.29 | 10 / 0 | |
| 4.6.28 | 10 / 0 | |
| 4.6.27 | 10 / 0 | |
| 4.6.26 | 10 / 0 | |
| 4.6.25 | 10 / 0 | |
| 4.6.24 | 10 / 0 | |
| 4.6.23 | 10 / 0 | |
| 4.6.22 | 10 / 0 | |
| 4.6.21 | 10 / 0 | |
| 4.6.20 | 10 / 0 | |
| 4.6.19 | 10 / 0 | |
| 4.6.18 | 10 / 0 | |
| 4.6.17 | 10 / 0 | |
| 4.6.16 | 10 / 0 | |
| 4.6.15 | 10 / 0 | |
| 4.6.14 | 10 / 0 | |
| 4.6.13 | 10 / 0 | |
| 4.6.12 | 10 / 0 | |
| 4.6.11 | 10 / 0 | |
| 4.6.10 | 10 / 0 | |
| 4.6.9 | 10 / 0 | |
| 4.6.8 | 10 / 0 | |
| 4.6.7 | 10 / 0 | |
| 4.6.6 | 10 / 0 | |
| 4.6.5 | 10 / 0 | |
| 4.6.4 | 10 / 0 | |
| 4.6.3 | 10 / 0 | |
| 4.6.2 | 10 / 0 | |
| 4.6.1 | 10 / 0 | |
| 4.6.0 | 10 / 0 | |
| 4.5.23 | 8 / 0 | |
| 4.5.22 | 8 / 0 | |
| 4.2.11 | 6 / 0 | |
| 4.2.10 | 6 / 0 | |
| 4.2.9 | 6 / 0 | |
| 4.2.8 | 6 / 0 | |
| 4.2.7 | 6 / 0 | |
| 4.2.6 | 6 / 0 | |
| 4.2.5 | 6 / 0 | |
| 4.2.4 | 6 / 0 | |
| 4.2.3 | 6 / 0 | |
| 4.2.2 | 6 / 0 | |
| 4.1.13 | 4 / 0 | |
| 4.1.12 | 4 / 0 | |
| 4.1.11 | 4 / 0 | |
| 4.1.10 | 4 / 0 | |
| 4.1.9 | 4 / 0 | |
| 4.1.8 | 4 / 0 | |
| 4.1.7 | 4 / 0 | |
| 4.1.6 | 4 / 0 | |
| 4.1.5 | 4 / 0 | |
| 4.1.4 | 4 / 0 | |
| 4.1.3 | 4 / 0 | |
| 4.1.2 | 4 / 0 | |
| 4.1.1 | 4 / 0 | |
| 4.1.0 | 4 / 0 | |
| 4.0.35 | 4 / 0 | |
| 4.0.34 | 4 / 0 | |
| 4.0.33 | 4 / 0 | |
| 4.0.32 | 4 / 0 | |
| 4.0.31 | 4 / 0 | |
| 4.0.30 | 4 / 0 | |
| 4.0.29 | 4 / 0 | |
| 4.0.28 | 4 / 0 | |
| 4.0.27 | 4 / 0 | |
| 4.0.26 | 4 / 0 | |
| 4.0.25 | 4 / 0 | |
| 4.0.24 | 4 / 0 | |
| 4.0.23 | 4 / 0 | |
| 4.0.22 | 4 / 0 | |
| 4.0.21 | 4 / 0 | |
| 4.0.20 | 4 / 0 | |
| 4.0.19 | 4 / 0 | |
| 4.0.18 | 4 / 0 | |
| 4.0.17 | 4 / 0 | |
| 4.0.16 | 4 / 0 | |
| 4.0.15 | 4 / 0 | |
| 4.0.14 | 4 / 0 | |
| 4.0.13 | 4 / 0 | |
| 4.0.12 | 4 / 0 | |
| 4.0.11 | 4 / 0 | |
| 4.0.10 | 4 / 0 | |
| 4.0.9 | 4 / 0 | |
| 4.0.8 | 4 / 0 | |
| 4.0.7 | 4 / 0 | |
| 4.0.6 | 4 / 0 | |
| 4.0.5 | 4 / 0 | |
| 4.0.4 | 4 / 0 | |
| 4.0.3 | 4 / 0 | |
| 4.0.2 | 4 / 0 | |
| 4.0.1 | 4 / 0 | |
| 4.0.0 | 4 / 0 |
v4.6.30
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.29
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.21
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.20
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.18
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.6.15
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.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.