@vue-storefront/nuxt
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@alokai/instrumentation-nuxt-module | AI (dependencies): First-party @alokai module matching package's Alokai/Nuxt function. | ai | |
| phantom-deps | phantom-dep:pinia | AI (phantom-deps): Nuxt module config wiring, not direct import; expected pattern. | ai | |
| phantom-deps | phantom-dep:@pinia/nuxt | AI (phantom-deps): Nuxt module config wiring, not direct import; expected pattern. | ai | |
| phantom-deps | phantom-dep:@alokai/instrumentation-nuxt-module | AI (phantom-deps): Nuxt module config wiring, not direct import; expected pattern. | ai | |
| typosquat | typosquat.levenshtein:next | AI (typosquat): Legitimate scoped Nuxt integration for Vue Storefront/Alokai; not a typosquat of 'next'. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 11.0.2 | 7 / 10 | |
| 11.0.1 | 7 / 10 | |
| 11.0.0 | 7 / 10 | |
| 10.0.0 | 7 / 8 |
v11.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-07-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
2 findingsThis version was published by a different npm account than previous versions on 2026-07-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-01. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.