@vee-validate/nuxt
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:next | AI (typosquat): Official vee-validate Nuxt integration by the library author; not a typosquat of 'next'. | ai | |
| phantom-deps | phantom-dep:vee-validate | AI (phantom-deps): vee-validate is a legitimate runtime dep used via Nuxt module config, not direct import. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 4.15.1 | 3 / 5 | |
| 4.15.0 | 3 / 5 | |
| 4.14.7 | 3 / 5 | |
| 4.14.6 | 3 / 5 | |
| 4.14.5 | 3 / 5 | |
| 4.14.4 | 3 / 5 | |
| 4.14.3 | 3 / 5 | |
| 4.14.2 | 3 / 5 | |
| 4.14.1 | 3 / 5 | |
| 4.14.0 | 3 / 5 | |
| 4.13.2 | 3 / 5 | |
| 4.13.1 | 3 / 5 | |
| 4.13.0 | 3 / 5 | |
| 4.12.8 | 3 / 5 | |
| 4.12.7 | 3 / 5 |
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.