@volar/vue-typescript
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@vue/compiler-sfc | AI (phantom-deps): Framework-scoped Vue dependency loaded by convention in language service; stable pattern. | ai | |
| phantom-deps | phantom-dep:@volar/vue-code-gen | AI (phantom-deps): Same-org scoped dependency used by convention in Volar monorepo; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@volar/pug-language-service | AI (phantom-deps): Same-org scoped dependency used by convention in Volar monorepo; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@vue/reactivity | AI (phantom-deps): Framework-scoped Vue dependency loaded by convention in language service; stable pattern. | ai | |
| phantom-deps | phantom-dep:@volar/code-gen | AI (phantom-deps): Same-org scoped dependency used by convention in Volar monorepo; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@volar/source-map | AI (phantom-deps): Same-org scoped dependency used by convention in Volar monorepo; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-known, widely-used Markdown parser; its use in Volar for SFC parsing is legitimate and expected. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads user-configured template compiler options from a config path; this is a legitimate plugin-loading pattern for a language service tool, not arbitrary code execution. | ai | |
| dependencies | unvetted-dep:@vue/compiler-sfc | AI (dependencies): @vue/compiler-sfc is the official Vue.js SFC compiler — a core, expected dependency for any Vue language tooling package. | ai |
Versions (showing 100 of 135)
| Version | Deps | Published |
|---|---|---|
| 1.6.5 | 2 / 0 | |
| 1.6.4 | 2 / 0 | |
| 1.6.3 | 2 / 0 | |
| 1.6.2 | 2 / 0 | |
| 1.6.1 | 2 / 0 | |
| 1.6.0 | 2 / 0 | |
| 1.5.4 | 2 / 0 | |
| 1.5.3 | 2 / 0 | |
| 1.5.2 | 2 / 0 | |
| 1.5.1 | 2 / 0 | |
| 1.5.0 | 2 / 0 | |
| 1.4.4 | 2 / 0 | |
| 1.4.3 | 2 / 0 | |
| 1.4.2 | 2 / 0 | |
| 1.4.1 | 2 / 0 | |
| 1.4.0 | 2 / 0 | |
| 1.3.19 | 2 / 0 | |
| 1.3.18 | 2 / 0 | |
| 1.3.17 | 2 / 0 | |
| 1.3.16 | 2 / 0 | |
| 1.3.15 | 2 / 0 | |
| 1.3.14 | 2 / 0 | |
| 1.3.13 | 2 / 0 | |
| 1.3.12 | 2 / 0 | |
| 1.3.11 | 2 / 0 | |
| 1.3.10 | 2 / 0 | |
| 1.3.9 | 2 / 0 | |
| 1.3.8 | 2 / 0 | |
| 1.3.7 | 2 / 0 | |
| 1.3.6 | 2 / 0 | |
| 1.3.5 | 2 / 0 | |
| 1.3.4 | 2 / 0 | |
| 1.3.3 | 2 / 0 | |
| 1.3.2 | 2 / 0 | |
| 1.3.1 | 2 / 0 | |
| 1.3.0 | 2 / 0 | |
| 1.2.1 | 2 / 0 | |
| 1.2.0 | 2 / 0 | |
| 1.1.7 | 2 / 0 | |
| 1.1.6 | 2 / 0 | |
| 1.1.5 | 2 / 0 | |
| 1.1.4 | 2 / 0 | |
| 1.1.3 | 2 / 0 | |
| 1.1.2 | 2 / 0 | |
| 1.1.0 | 2 / 0 | |
| 1.0.24 | 2 / 0 | |
| 1.0.22 | 2 / 0 | |
| 1.0.21 | 2 / 0 | |
| 1.0.20 | 2 / 0 | |
| 1.0.19 | 2 / 0 | |
| 1.0.18 | 2 / 0 | |
| 1.0.17 | 2 / 0 | |
| 1.0.16 | 2 / 0 | |
| 1.0.14 | 2 / 0 | |
| 1.0.13 | 2 / 0 | |
| 1.0.12 | 2 / 0 | |
| 1.0.11 | 2 / 0 | |
| 1.0.10 | 2 / 0 | |
| 1.0.9 | 2 / 0 | |
| 1.0.8 | 2 / 0 | |
| 1.0.7 | 2 / 0 | |
| 1.0.6 | 2 / 0 | |
| 1.0.5 | 2 / 0 | |
| 1.0.4 | 2 / 0 | |
| 1.0.3 | 2 / 0 | |
| 1.0.2 | 2 / 0 | |
| 1.0.1 | 2 / 0 | |
| 1.0.0 | 2 / 0 | |
| 0.40.13 | 3 / 1 | |
| 0.40.12 | 3 / 1 | |
| 0.40.11 | 3 / 1 | |
| 0.40.10 | 3 / 1 | |
| 0.40.9 | 3 / 1 | |
| 0.40.8 | 3 / 1 | |
| 0.40.7 | 3 / 1 | |
| 0.40.6 | 3 / 1 | |
| 0.40.5 | 3 / 1 | |
| 0.40.4 | 3 / 1 | |
| 0.40.3 | 3 / 1 | |
| 0.40.2 | 3 / 1 | |
| 0.40.1 | 3 / 1 | |
| 0.40.0 | 3 / 1 | |
| 0.39.5 | 3 / 1 | |
| 0.39.4 | 3 / 1 | |
| 0.39.3 | 3 / 1 | |
| 0.39.2 | 3 / 1 | |
| 0.39.0 | 3 / 1 | |
| 0.38.9 | 5 / 2 | |
| 0.38.8 | 5 / 2 | |
| 0.38.7 | 5 / 2 | |
| 0.38.5 | 5 / 2 | |
| 0.38.4 | 5 / 2 | |
| 0.38.3 | 5 / 2 | |
| 0.38.2 | 5 / 2 | |
| 0.38.1 | 5 / 2 | |
| 0.38.0 | 5 / 2 | |
| 0.37.9 | 5 / 2 | |
| 0.37.8 | 5 / 2 | |
| 0.37.7 | 5 / 2 | |
| 0.37.5 | 5 / 2 |
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
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.2
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.39.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.