← Home

@nuxtjs/opencollective

npm Repository Homepage

[![npm version][npm-v-src]][npm-v-href] [![npm downloads][npm-d-src]][npm-d-href] [![status][github-actions-src]][github-actions-href]

5
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

clarkdopi0atinuxalexchopinmannil

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from mannil to pi0 is a legitimate transition within the @nuxtjs/Nuxt core team. ai
maintainer-change maintainer-added AI (maintainer-change): Added maintainers (alexchopin, atinux, clarkdo, pi0) are all known Nuxt.js core team members. ai

Versions (showing 5 of 5)

Version Deps Published
0.3.2 3 / 11
0.2.2 3 / 19
0.2.1 3 / 19
0.2.0 3 / 19
0.1.0 4 / 17

v0.3.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.1

2 findings
HIGH Publisher changed: mannil → pi0 (on 2018-12-13) provenance

This version was published by a different npm account than previous versions on 2018-12-13. 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.

v0.2.0

2 findings
HIGH Publisher changed: mannil → pi0 (on 2018-11-25) provenance

This version was published by a different npm account than previous versions on 2018-11-25. 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.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.