@wzyjs/next
description
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:nuxt | AI (typosquat): Scoped package @wzyjs/next; not impersonating nuxt, different namespace and purpose. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped package @wzyjs/next; not impersonating jest, different namespace and purpose. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): Scoped package @wzyjs/next; not impersonating knex, different namespace and purpose. | ai | |
| phantom-deps | phantom-dep:@zenstackhq/sdk | AI (phantom-deps): @zenstackhq/sdk is declared as a dependency; used in config files as a ZenStack plugin dependency. | ai |
Versions (showing 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 0.3.41 | 1 / 2 | |
| 0.3.39 | 1 / 2 | |
| 0.3.38 | 1 / 2 | |
| 0.3.37 | 1 / 2 | |
| 0.3.36 | 1 / 2 | |
| 0.3.32 | 1 / 2 | |
| 0.3.31 | 1 / 2 | |
| 0.3.30 | 1 / 2 | |
| 0.3.29 | 1 / 2 | |
| 0.3.28 | 1 / 0 | |
| 0.3.27 | 1 / 0 | |
| 0.3.26 | 1 / 0 | |
| 0.3.25 | 1 / 0 | |
| 0.3.24 | 1 / 0 | |
| 0.3.23 | 1 / 0 | |
| 0.3.22 | 1 / 0 | |
| 0.3.20 | 1 / 0 | |
| 0.3.18 | 1 / 0 | |
| 0.3.17 | 1 / 0 | |
| 0.3.16 | 1 / 0 | |
| 0.3.10 | 1 / 0 | |
| 0.3.9 | 1 / 0 | |
| 0.3.8 | 1 / 0 | |
| 0.3.7 | 1 / 0 | |
| 0.3.6 | 1 / 0 | |
| 0.3.4 | 1 / 0 | |
| 0.3.3 | 1 / 0 | |
| 0.3.2 | 1 / 0 | |
| 0.3.1 | 1 / 0 | |
| 0.3.0 | 1 / 0 | |
| 0.2.83 | 1 / 0 | |
| 0.2.74 | 1 / 0 | |
| 0.2.73 | 1 / 0 | |
| 0.2.72 | 1 / 0 | |
| 0.2.71 | 1 / 0 | |
| 0.2.69 | 1 / 0 | |
| 0.2.67 | 1 / 0 | |
| 0.2.66 | 1 / 0 | |
| 0.2.65 | 1 / 0 | |
| 0.2.64 | 1 / 0 | |
| 0.2.63 | 1 / 0 | |
| 0.2.62 | 1 / 0 | |
| 0.2.61 | 1 / 0 | |
| 0.2.60 | 1 / 0 | |
| 0.2.59 | 1 / 0 | |
| 0.2.58 | 1 / 0 | |
| 0.2.57 | 1 / 0 | |
| 0.2.56 | 1 / 0 | |
| 0.2.55 | 1 / 0 | |
| 0.2.54 | 1 / 0 | |
| 0.2.53 | 1 / 0 | |
| 0.2.52 | 1 / 0 | |
| 0.2.51 | 1 / 0 | |
| 0.2.50 | 1 / 0 | |
| 0.2.49 | 1 / 0 | |
| 0.2.48 | 1 / 0 | |
| 0.2.47 | 1 / 0 | |
| 0.2.46 | 1 / 0 | |
| 0.2.44 | 1 / 0 | |
| 0.2.43 | 1 / 0 | |
| 0.2.42 | 1 / 0 | |
| 0.2.41 | 1 / 0 | |
| 0.2.40 | 1 / 0 |
v0.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.41
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.