@nextclaw/ncp
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:yup | AI (typosquat): Scoped package @nextclaw/ncp is unrelated to yup; edit-distance match is coincidental. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 0.7.13 | 0 / 3 | |
| 0.7.12 | 0 / 3 | |
| 0.7.11 | 0 / 3 | |
| 0.7.10 | 0 / 3 | |
| 0.7.9 | 0 / 3 | |
| 0.7.8 | 0 / 3 | |
| 0.7.7 | 0 / 3 | |
| 0.7.6 | 0 / 3 | |
| 0.7.5 | 0 / 3 | |
| 0.7.4 | 0 / 3 | |
| 0.7.3 | 0 / 3 | |
| 0.7.2 | 0 / 3 | |
| 0.7.1 | 0 / 3 | |
| 0.7.0 | 0 / 3 | |
| 0.6.6 | 0 / 3 | |
| 0.6.5 | 0 / 3 | |
| 0.6.4 | 0 / 3 | |
| 0.6.3 | 0 / 3 | |
| 0.6.2 | 0 / 3 | |
| 0.6.1 | 0 / 3 | |
| 0.6.0 | 0 / 3 | |
| 0.5.28 | 0 / 3 | |
| 0.5.27 | 0 / 3 | |
| 0.5.26 | 0 / 3 | |
| 0.5.25 | 0 / 3 | |
| 0.5.24 | 0 / 3 | |
| 0.5.23 | 0 / 3 | |
| 0.5.22 | 0 / 3 | |
| 0.5.21 | 0 / 3 | |
| 0.5.20 | 0 / 3 | |
| 0.5.19 | 0 / 3 | |
| 0.5.18 | 0 / 3 | |
| 0.5.17 | 0 / 3 | |
| 0.5.16 | 0 / 3 | |
| 0.5.15 | 0 / 3 | |
| 0.5.14 | 0 / 3 | |
| 0.5.13 | 0 / 3 | |
| 0.5.12 | 0 / 3 | |
| 0.5.11 | 0 / 3 | |
| 0.5.10 | 0 / 3 | |
| 0.5.9 | 0 / 3 | |
| 0.5.8 | 0 / 3 | |
| 0.5.7 | 0 / 3 | |
| 0.5.6 | 0 / 3 | |
| 0.5.5 | 0 / 3 | |
| 0.5.4 | 0 / 3 | |
| 0.5.3 | 0 / 3 | |
| 0.5.2 | 0 / 3 | |
| 0.5.1 | 0 / 3 | |
| 0.5.0 | 0 / 4 | |
| 0.4.6 | 0 / 4 |
v0.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.