@primevue/nuxt-module
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@primevue/forms | AI (dependencies): Same-org (@primevue) sibling package; part of the PrimeVue ecosystem bundle. | ai | |
| phantom-deps | phantom-dep:@primevue/forms | AI (phantom-deps): First-party @primevue monorepo dep; re-exported rather than directly imported — stable false positive. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.5.5 | 9 / 11 | |
| 4.5.4 | 9 / 11 | |
| 4.5.3 | 9 / 11 | |
| 4.3.8 | 9 / 11 | |
| 4.3.6 | 8 / 11 | |
| 4.3.5 | 8 / 11 |
v4.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.