rollup-plugin-vue
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): yyx990803 (Evan You) is the Vue framework author; legitimate maintainer transition for v6/Vue 3 rewrite. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): yyx990803 is the Vue creator; expected maintainer for Vue ecosystem packages. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Major version rewrite (v5→v6 for Vue 3); large diff is expected. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 6.0.0 | 3 / 15 | |
| 5.1.9 | 9 / 37 | |
| 5.1.8 | 9 / 37 | |
| 5.1.7 | 9 / 37 | |
| 5.1.6 | 9 / 37 | |
| 5.1.5 | 9 / 37 | |
| 5.1.4 | 9 / 37 | |
| 5.1.3 | 9 / 37 | |
| 5.1.2 | 9 / 37 | |
| 5.1.1 | 9 / 37 | |
| 5.1.0 | 9 / 37 | |
| 5.0.1 | 9 / 37 | |
| 5.0.0 | 9 / 37 | |
| 4.7.2 | 9 / 37 | |
| 4.7.1 | 9 / 37 | |
| 4.7.0 | 9 / 37 | |
| 4.6.2 | 8 / 37 | |
| 4.6.1 | 8 / 37 | |
| 4.6.0 | 8 / 37 | |
| 4.5.0 | 9 / 35 | |
| 4.4.0 | 8 / 35 | |
| 4.3.2 | 7 / 34 | |
| 4.3.1 | 7 / 34 | |
| 4.3.0 | 7 / 34 | |
| 4.2.0 | 8 / 29 | |
| 4.1.5 | 8 / 29 | |
| 4.1.4 | 8 / 28 | |
| 4.1.3 | 7 / 27 | |
| 4.1.2 | 7 / 27 | |
| 4.1.1 | 7 / 27 | |
| 4.1.0 | 7 / 27 | |
| 4.0.2 | 7 / 20 | |
| 4.0.1 | 6 / 18 | |
| 4.0.0 | 6 / 18 | |
| 3.0.0 | 25 / 21 | |
| 2.5.4 | 26 / 21 | |
| 2.5.3 | 26 / 21 | |
| 2.5.2 | 25 / 21 | |
| 2.5.1 | 26 / 20 | |
| 2.5.0 | 25 / 21 | |
| 2.4.2 | 25 / 19 | |
| 2.4.1 | 25 / 19 | |
| 2.4.0 | 24 / 19 | |
| 2.3.1 | 22 / 19 | |
| 2.3.0 | 22 / 19 | |
| 2.2.21 | 9 / 21 | |
| 2.2.20 | 9 / 21 | |
| 2.2.19 | 9 / 21 | |
| 2.2.18 | 9 / 21 | |
| 2.2.17 | 9 / 21 | |
| 2.2.16 | 8 / 21 |
v6.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: yyx990803.
This version was published by a different npm account than previous versions on 2020-11-25. 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.
v5.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.