@swapkit/tokens
SwapKit - Tokens
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
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.4.1 | 0 / 2 | |
| 4.4.0 | 0 / 2 | |
| 4.3.5 | 0 / 2 | |
| 4.3.4 | 0 / 2 | |
| 4.3.3 | 0 / 2 | |
| 4.3.2 | 0 / 2 | |
| 4.3.1 | 0 / 2 | |
| 4.3.0 | 0 / 2 | |
| 4.2.8 | 0 / 2 | |
| 4.2.7 | 1 / 2 | |
| 4.2.6 | 1 / 2 | |
| 4.2.5 | 1 / 2 | |
| 4.2.4 | 1 / 2 | |
| 4.2.3 | 1 / 2 | |
| 4.1.2 | 1 / 2 | |
| 4.1.1 | 1 / 2 |
v4.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.2
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.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.