@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 51 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 |
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.