@vue-storefront/next
Alokai dedicated features for Next.js
3
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
filrakfifciuumtokarskivsfdzalewskirickrohrigwojciechsikora
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publishing via GitHub Actions CI is standard practice; consistent with org-level automation adoption. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 69 versions; lack of Sigstore attestation is a minor gap, not a security signal. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): Scoped @vue-storefront package; legitimate Alokai/VSF ecosystem, not a nuxt typosquat. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): Scoped @vue-storefront package; 2-edit distance to jest is coincidental, not a typosquat. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): Scoped @vue-storefront package; 2-edit distance to knex is coincidental, not a typosquat. | ai |
v8.0.1
2 findings
HIGH
Publisher changed: filrak → GitHub Actions (on 2026-07-02)
provenance
This 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.
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.