@volar/vue-language-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): muggle-string is a small, benign utility dep, not an attack vector. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is a best practice but not a blocker for established packages with strong publisher track record. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Missing description is benign for an established scoped package from a trusted publisher with 112 prior versions. | ai | |
| dependencies | unvetted-dep:vue-template-compiler | AI (dependencies): vue-template-compiler is the official Vue 2 template compiler from the vuejs org; a legitimate and expected dependency for Vue language tooling. | ai | |
| dependencies | unvetted-dep:muggle-string | AI (dependencies): muggle-string is a utility package authored by the same maintainer (johnsoncodehk) as part of the Volar ecosystem; not a risk. | ai | |
| dependencies | unvetted-dep:@vue/compiler-sfc | AI (dependencies): Standard Vue ecosystem dependency; appropriate for Vue language service package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is used for controlled plugin loading with path resolution constrained to rootDir; legitimate pattern for this package. | ai | |
| dependencies | unvetted-dep:@vue/compiler-core | AI (dependencies): Standard Vue ecosystem dependency; appropriate for Vue language service package. | ai |
Versions (showing 87 of 87)
| Version | Deps | Published |
|---|---|---|
| 1.6.5 | 9 / 1 | |
| 1.6.4 | 9 / 1 | |
| 1.6.3 | 9 / 1 | |
| 1.6.2 | 9 / 1 | |
| 1.6.1 | 9 / 1 | |
| 1.6.0 | 9 / 1 | |
| 1.5.4 | 9 / 1 | |
| 1.5.3 | 9 / 1 | |
| 1.5.2 | 9 / 1 | |
| 1.5.1 | 9 / 1 | |
| 1.5.0 | 9 / 1 | |
| 1.4.4 | 9 / 1 | |
| 1.4.3 | 9 / 1 | |
| 1.4.2 | 9 / 1 | |
| 1.4.1 | 9 / 1 | |
| 1.4.0 | 9 / 1 | |
| 1.3.19 | 9 / 1 | |
| 1.3.18 | 9 / 1 | |
| 1.3.17 | 9 / 1 | |
| 1.3.16 | 9 / 1 | |
| 1.3.15 | 9 / 1 | |
| 1.3.14 | 9 / 1 | |
| 1.3.13 | 9 / 1 | |
| 1.3.12 | 9 / 1 | |
| 1.3.11 | 9 / 1 | |
| 1.3.10 | 9 / 1 | |
| 1.3.9 | 9 / 1 | |
| 1.3.8 | 9 / 1 | |
| 1.3.7 | 9 / 1 | |
| 1.3.6 | 9 / 1 | |
| 1.3.5 | 9 / 1 | |
| 1.3.4 | 9 / 1 | |
| 1.3.3 | 9 / 1 | |
| 1.3.2 | 9 / 1 | |
| 1.3.1 | 9 / 1 | |
| 1.3.0 | 9 / 1 | |
| 1.2.1 | 9 / 1 | |
| 1.2.0 | 9 / 1 | |
| 1.1.7 | 9 / 1 | |
| 1.1.6 | 9 / 1 | |
| 1.1.5 | 9 / 1 | |
| 1.1.4 | 9 / 1 | |
| 1.1.3 | 9 / 1 | |
| 1.1.2 | 9 / 1 | |
| 1.1.0 | 9 / 1 | |
| 1.0.24 | 8 / 1 | |
| 1.0.22 | 8 / 1 | |
| 1.0.21 | 8 / 1 | |
| 1.0.20 | 8 / 1 | |
| 1.0.19 | 8 / 1 | |
| 1.0.18 | 8 / 1 | |
| 1.0.17 | 8 / 1 | |
| 1.0.16 | 8 / 1 | |
| 1.0.14 | 8 / 1 | |
| 1.0.13 | 8 / 1 | |
| 1.0.12 | 8 / 1 | |
| 1.0.11 | 8 / 1 | |
| 1.0.10 | 8 / 1 | |
| 1.0.9 | 8 / 1 | |
| 1.0.8 | 8 / 1 | |
| 1.0.7 | 8 / 1 | |
| 1.0.6 | 8 / 1 | |
| 1.0.5 | 8 / 1 | |
| 1.0.4 | 8 / 1 | |
| 1.0.3 | 8 / 1 | |
| 1.0.2 | 8 / 1 | |
| 1.0.1 | 8 / 1 | |
| 1.0.0 | 8 / 1 | |
| 0.40.13 | 7 / 2 | |
| 0.40.12 | 7 / 2 | |
| 0.40.11 | 7 / 2 | |
| 0.40.10 | 7 / 2 | |
| 0.40.9 | 7 / 2 | |
| 0.40.8 | 7 / 2 | |
| 0.40.7 | 7 / 2 | |
| 0.40.6 | 7 / 2 | |
| 0.40.5 | 7 / 2 | |
| 0.40.4 | 7 / 2 | |
| 0.40.3 | 7 / 2 | |
| 0.40.2 | 7 / 2 | |
| 0.40.1 | 7 / 2 | |
| 0.40.0 | 7 / 2 | |
| 0.39.5 | 5 / 2 | |
| 0.39.4 | 5 / 2 | |
| 0.39.3 | 5 / 2 | |
| 0.39.2 | 5 / 2 | |
| 0.39.0 | 5 / 2 |
v1.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.