@vue/component-compiler
bundler agnostic API for compiling Vue SFC
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:digital-cult.com | AI (email-domain): Theoretical domain hijack risk for a well-established Vue.js org package by a known contributor. No active exploit; package code and repo are legitimate. | ai | |
| provenance | no-provenance | AI (provenance): Established package predating Sigstore provenance workflows; no provenance is expected and not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:less | AI (phantom-deps): less is an optionalDependency for Vue SFC style preprocessing; pattern is stable and expected for this package. | ai | |
| phantom-deps | phantom-dep:sass | AI (phantom-deps): sass is an optionalDependency for Vue SFC style preprocessing; pattern is stable and expected for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): antfu, posva, yyx990803, soda are well-known Vue.js core team members, not spam publishers. This is a stable false positive for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers (antfu, posva, pikax, etc.) are recognized Vue.js core team members under the vuejs org. Legitimate team transition, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): chrisvfritz is a former Vue team member; removal is consistent with legitimate team restructuring within the vuejs org. | ai | |
| phantom-deps | phantom-dep:stylus | AI (phantom-deps): stylus is an optionalDependency for Vue SFC style preprocessing; pattern is stable and expected for this package. | ai | |
| phantom-deps | phantom-dep:pug | AI (phantom-deps): pug is an optionalDependency for Vue SFC template preprocessing; not directly imported in source is expected for optional preprocessor support. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.2.4 | 9 / 20 | |
| 4.2.3 | 9 / 20 | |
| 4.2.2 | 9 / 20 | |
| 4.2.1 | 9 / 20 | |
| 4.2.0 | 9 / 20 | |
| 4.1.0 | 9 / 20 | |
| 4.0.0 | 9 / 20 | |
| 3.6.0 | 5 / 20 | |
| 3.5.0 | 5 / 20 | |
| 3.4.5 | 5 / 20 | |
| 3.4.4 | 5 / 20 | |
| 3.4.3 | 5 / 20 | |
| 3.4.2 | 5 / 20 | |
| 3.4.1 | 5 / 20 | |
| 3.4.0 | 5 / 20 | |
| 3.3.3 | 4 / 20 | |
| 3.3.2 | 4 / 20 | |
| 3.3.1 | 4 / 20 | |
| 3.3.0 | 4 / 20 | |
| 3.2.0 | 4 / 20 | |
| 3.1.1 | 4 / 20 | |
| 3.1.0 | 4 / 20 | |
| 3.0.0 | 4 / 19 |
v4.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.3
2 findingsMaintainer email '[email protected]' uses domain 'digital-cult.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.