@swapkit/wallet-core
SwapKit - Wallet Core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): SwapKit publishes via GitHub Actions without Sigstore attestation; consistent across all versions in this monorepo. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 4.3.21 | 1 / 0 | |
| 4.3.20 | 1 / 0 | |
| 4.3.19 | 1 / 0 | |
| 4.3.18 | 1 / 0 | |
| 4.3.17 | 1 / 0 | |
| 4.3.16 | 1 / 0 | |
| 4.3.14 | 1 / 0 | |
| 4.3.13 | 1 / 0 | |
| 4.3.12 | 1 / 0 | |
| 4.3.11 | 1 / 0 | |
| 4.3.10 | 1 / 0 | |
| 4.3.9 | 1 / 0 | |
| 4.3.8 | 1 / 0 | |
| 4.3.7 | 1 / 0 | |
| 4.3.6 | 1 / 0 | |
| 4.3.5 | 1 / 0 | |
| 4.3.4 | 1 / 0 | |
| 4.3.3 | 1 / 0 | |
| 4.3.2 | 1 / 0 | |
| 4.3.1 | 1 / 0 | |
| 4.3.0 | 1 / 0 | |
| 4.2.8 | 1 / 0 | |
| 4.2.7 | 1 / 0 | |
| 4.2.6 | 1 / 0 | |
| 4.2.5 | 1 / 0 | |
| 4.2.4 | 1 / 0 | |
| 4.2.3 | 1 / 0 | |
| 4.2.2 | 1 / 0 | |
| 4.2.1 | 1 / 0 | |
| 4.2.0 | 1 / 0 | |
| 4.1.29 | 1 / 0 | |
| 4.1.28 | 1 / 0 | |
| 4.1.27 | 1 / 0 | |
| 4.1.26 | 1 / 0 | |
| 4.1.25 | 1 / 0 | |
| 4.1.24 | 1 / 0 | |
| 4.1.23 | 1 / 0 | |
| 4.0.53 | 1 / 0 | |
| 4.0.52 | 1 / 0 | |
| 4.0.51 | 1 / 0 | |
| 4.0.50 | 1 / 0 | |
| 4.0.49 | 1 / 0 | |
| 4.0.48 | 1 / 0 | |
| 4.0.47 | 1 / 0 | |
| 4.0.46 | 1 / 0 | |
| 4.0.43 | 1 / 0 | |
| 4.0.42 | 1 / 0 | |
| 4.0.41 | 1 / 0 | |
| 4.0.40 | 1 / 0 | |
| 4.0.39 | 1 / 0 | |
| 4.0.38 | 1 / 0 |
v4.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.