vue-component-compiler
Compiler for single file Vue components
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Package is 11+ years old, published by Evan You (Vue.js creator) under the vuejs org. Provenance attestation predates this package's era; absence is expected and not a risk signal. | ai | |
| dependencies | unvetted-dep:html-minifier | AI (dependencies): html-minifier is a well-known, established package used legitimately for HTML minification in this Vue component compiler. No malicious signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): yyx990803 is Evan You, creator of Vue.js. The SPAM-FLAGGED signal is a false positive for this well-known, legitimate publisher under the official vuejs GitHub org. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads user's own vue.config.js from cwd — intentional build-tool configuration pattern, not arbitrary code injection. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 4 / 8 | |
| 1.1.3 | 4 / 8 | |
| 1.1.0 | 4 / 6 | |
| 1.0.3 | 4 / 6 | |
| 1.0.2 | 3 / 6 | |
| 1.0.1 | 3 / 0 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.