@swapkit/server
SwapKit - Server SDK
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped @swapkit/* monorepo package; name similarity to semver is coincidental, not a squatting attempt. | ai |
Versions (showing 51 of 104)
| Version | Deps | Published |
|---|---|---|
| 4.4.5 | 4 / 0 | |
| 4.4.4 | 4 / 0 | |
| 4.4.3 | 4 / 0 | |
| 4.4.2 | 4 / 0 | |
| 4.4.1 | 4 / 0 | |
| 4.4.0 | 4 / 0 | |
| 4.3.17 | 4 / 0 | |
| 4.3.15 | 4 / 0 | |
| 4.3.14 | 4 / 0 | |
| 4.3.13 | 4 / 0 | |
| 4.3.12 | 4 / 0 | |
| 4.3.11 | 4 / 0 | |
| 4.3.10 | 4 / 0 | |
| 4.3.9 | 4 / 0 | |
| 4.3.8 | 4 / 0 | |
| 4.3.7 | 4 / 0 | |
| 4.3.6 | 4 / 0 | |
| 4.3.5 | 4 / 0 | |
| 4.3.4 | 4 / 0 | |
| 4.3.3 | 4 / 0 | |
| 4.3.2 | 4 / 0 | |
| 4.3.1 | 4 / 0 | |
| 4.3.0 | 4 / 0 | |
| 4.2.56 | 4 / 0 | |
| 4.2.55 | 4 / 0 | |
| 4.2.54 | 4 / 0 | |
| 4.2.53 | 4 / 0 | |
| 4.2.52 | 4 / 0 | |
| 4.2.51 | 4 / 0 | |
| 4.2.50 | 4 / 0 | |
| 4.2.49 | 4 / 0 | |
| 4.2.48 | 5 / 0 | |
| 4.2.47 | 5 / 0 | |
| 4.2.46 | 5 / 0 | |
| 4.2.45 | 5 / 0 | |
| 4.2.44 | 5 / 0 | |
| 4.2.43 | 5 / 0 | |
| 4.2.42 | 5 / 0 | |
| 4.2.41 | 5 / 0 | |
| 4.2.40 | 5 / 0 | |
| 4.2.39 | 5 / 0 | |
| 4.2.38 | 5 / 0 | |
| 4.2.37 | 5 / 0 | |
| 4.2.36 | 5 / 0 | |
| 4.2.35 | 5 / 0 | |
| 4.2.34 | 5 / 0 | |
| 4.2.33 | 5 / 0 | |
| 4.2.32 | 5 / 0 | |
| 4.2.31 | 5 / 0 | |
| 4.2.30 | 5 / 0 | |
| 4.2.29 | 5 / 0 |
v4.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.