@nuxt/opencollective
[![npm version][npm-v-src]][npm-v-href] [![npm downloads][npm-d-src]][npm-d-href] [![status][github-actions-src]][github-actions-href]
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Stale 2022 transition to known Nuxt maintainers, long-stable since. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same stale ownership transition, not a takeover pattern. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Publisher change is 1524d old and stable, inconsistent with compromise. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 1 / 13 | |
| 0.4.0 | 3 / 12 | |
| 0.3.3 | 3 / 11 | |
| 0.3.2 | 3 / 11 | |
| 0.3.1 | 3 / 11 | |
| 0.3.0 | 3 / 19 | |
| 0.2.2 | 3 / 19 | |
| 0.2.1 | 3 / 19 | |
| 0.2.0 | 3 / 19 |
v0.4.0
2 findingsThis version was published by a different npm account (danielroe) than the most recent previously approved version (pi0) on 2023-11-17. It has since remained available on npm for 976 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
2 findingsThis version was published by a different npm account (danielroe) than the most recent previously approved version (pi0) on 2022-05-18. It has since remained available on npm for 1524 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pi0) than the most recent previously approved version (mannil) on 2020-10-13, but pi0 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pi0) than the most recent previously approved version (mannil) on 2020-10-13, but pi0 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (mannil) than the most recent previously approved version (pi0) on 2019-08-26, but mannil is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.