@vue/component-compiler-utils
Lower level utilities for compiling Vue single file 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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:coverage/lcov-report/prettify.js | AI (source-diff): This is the standard Google Code Prettify JS bundled by Istanbul into HTML coverage reports. It is a test artifact under coverage/ with no runtime impact on package consumers. | ai | |
| provenance | publisher-changed | AI (provenance): znck is a known Vue.js core contributor; the transition from yyx990803 to znck is a documented legitimate maintainer handoff for this official vuejs org package. | ai | |
| provenance | missing-githead | AI (provenance): Missing gitHead is a minor publish environment difference; no other indicators of compromise and the diff shows no material changes. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 3.3.0 | 9 / 14 | |
| 3.2.2 | 9 / 14 | |
| 3.1.1 | 9 / 14 | |
| 3.1.0 | 9 / 14 | |
| 3.0.2 | 9 / 14 | |
| 3.0.1 | 9 / 14 | |
| 3.0.0 | 9 / 14 | |
| 2.6.0 | 9 / 14 | |
| 2.5.2 | 9 / 14 | |
| 2.5.1 | 9 / 14 | |
| 2.5.0 | 9 / 14 | |
| 2.4.0 | 9 / 14 | |
| 2.3.1 | 9 / 14 | |
| 2.3.0 | 9 / 14 | |
| 2.2.0 | 9 / 13 | |
| 2.1.2 | 9 / 13 | |
| 2.1.1 | 9 / 13 | |
| 2.1.0 | 9 / 13 | |
| 2.0.0 | 9 / 11 | |
| 1.3.1 | 9 / 11 | |
| 1.3.0 | 9 / 11 | |
| 1.2.1 | 9 / 11 | |
| 1.2.0 | 9 / 11 | |
| 1.1.0 | 9 / 11 | |
| 1.0.0 | 8 / 6 |
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-11-04. This could indicate a legitimate maintainer transition or an account compromise.
v3.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: znck.
This version was published by a different npm account than previous versions on 2019-04-11. 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.
v2.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-02-21. This could indicate a legitimate maintainer transition or an account compromise.
v2.5.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-31. This could indicate a legitimate maintainer transition or an account compromise.
v2.5.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-25. This could indicate a legitimate maintainer transition or an account compromise.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-01-02. This could indicate a legitimate maintainer transition or an account compromise.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.