@privateaim/kit
[![npm version][npm-src]][npm-href]
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:koa | AI (typosquat): Scoped package @privateaim/kit; Levenshtein match to 'koa' is a false positive for this org. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): Scoped package @privateaim/kit; Levenshtein match to 'vite' is a false positive for this org. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): Scoped package @privateaim/kit; Levenshtein match to 'got' is a false positive for this org. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 0.12.5 | 2 / 5 | |
| 0.12.4 | 2 / 5 | |
| 0.12.2 | 2 / 5 | |
| 0.12.1 | 2 / 5 | |
| 0.12.0 | 2 / 5 | |
| 0.11.5 | 2 / 5 | |
| 0.11.4 | 2 / 5 | |
| 0.11.3 | 2 / 5 | |
| 0.11.2 | 2 / 5 | |
| 0.11.1 | 2 / 5 | |
| 0.11.0 | 2 / 5 | |
| 0.10.3 | 2 / 5 | |
| 0.10.2 | 2 / 5 | |
| 0.10.1 | 2 / 5 | |
| 0.10.0 | 2 / 5 | |
| 0.8.43 | 3 / 2 | |
| 0.8.42 | 3 / 2 | |
| 0.8.41 | 3 / 2 | |
| 0.8.39 | 3 / 2 | |
| 0.8.38 | 3 / 2 | |
| 0.8.37 | 3 / 2 | |
| 0.8.36 | 3 / 2 | |
| 0.8.34 | 3 / 2 | |
| 0.8.33 | 3 / 2 | |
| 0.8.32 | 3 / 2 | |
| 0.8.31 | 3 / 2 | |
| 0.8.30 | 3 / 2 | |
| 0.8.29 | 3 / 2 | |
| 0.8.28 | 3 / 2 | |
| 0.8.27 | 1 / 2 | |
| 0.8.26 | 1 / 2 | |
| 0.8.25 | 1 / 2 | |
| 0.8.23 | 1 / 2 | |
| 0.8.22 | 1 / 2 | |
| 0.8.21 | 1 / 2 | |
| 0.8.20 | 1 / 2 | |
| 0.8.19 | 1 / 2 | |
| 0.8.18 | 1 / 2 | |
| 0.8.17 | 1 / 2 | |
| 0.8.16 | 1 / 2 | |
| 0.8.12 | 1 / 1 | |
| 0.8.11 | 1 / 1 | |
| 0.8.10 | 1 / 1 | |
| 0.8.9 | 1 / 1 | |
| 0.8.8 | 1 / 1 | |
| 0.8.7 | 1 / 1 | |
| 0.8.6 | 1 / 1 | |
| 0.8.5 | 1 / 1 | |
| 0.8.4 | 1 / 1 | |
| 0.8.3 | 1 / 1 | |
| 0.8.2 | 1 / 1 |
v0.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.