@volar/typescript-language-service
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:upath | AI (phantom-deps): Runtime dependency for path manipulation in TypeScript language service; legitimate indirect usage. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Runtime dependency for version comparison; legitimate indirect usage in language service. | ai | |
| phantom-deps | phantom-dep:vscode-nls | AI (phantom-deps): Runtime dependency for VSCode language service integration; legitimate indirect usage. | ai | |
| phantom-deps | phantom-dep:@volar/shared | AI (phantom-deps): Monorepo sibling dependency; legitimate shared utilities for Volar packages. | ai | |
| phantom-deps | phantom-dep:vscode-languageserver-protocol | AI (phantom-deps): Core runtime dependency for VSCode language server protocol; legitimate for language service. | ai | |
| phantom-deps | phantom-dep:vscode-languageserver-textdocument | AI (phantom-deps): Core runtime dependency for text document handling; legitimate for language service. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 6 / 1 | |
| 1.0.0 | 6 / 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 | 6 / 2 | |
| 0.40.4 | 6 / 2 | |
| 0.40.3 | 6 / 2 | |
| 0.40.2 | 6 / 2 | |
| 0.40.1 | 6 / 2 | |
| 0.40.0 | 6 / 2 | |
| 0.39.5 | 6 / 2 | |
| 0.39.4 | 6 / 2 | |
| 0.39.3 | 6 / 2 | |
| 0.39.2 | 6 / 2 | |
| 0.39.0 | 6 / 2 | |
| 0.38.9 | 6 / 2 | |
| 0.38.8 | 6 / 2 | |
| 0.38.7 | 6 / 2 | |
| 0.38.5 | 6 / 2 | |
| 0.38.4 | 6 / 2 | |
| 0.38.3 | 6 / 2 | |
| 0.38.2 | 6 / 2 | |
| 0.38.1 | 6 / 2 | |
| 0.38.0 | 6 / 2 | |
| 0.37.9 | 6 / 2 | |
| 0.37.8 | 6 / 2 | |
| 0.37.7 | 6 / 2 | |
| 0.37.5 | 6 / 2 | |
| 0.37.4 | 6 / 2 | |
| 0.37.3 | 6 / 2 | |
| 0.37.2 | 6 / 2 | |
| 0.37.1 | 6 / 2 | |
| 0.37.0 | 6 / 2 | |
| 0.36.1 | 6 / 2 | |
| 0.36.0 | 6 / 2 | |
| 0.35.2 | 6 / 2 | |
| 0.35.1 | 6 / 2 | |
| 0.35.0 | 6 / 2 | |
| 0.34.17 | 6 / 2 | |
| 0.34.16 | 6 / 2 | |
| 0.34.15 | 6 / 2 | |
| 0.34.13 | 6 / 2 | |
| 0.34.12 | 6 / 2 | |
| 0.34.11 | 6 / 2 | |
| 0.34.10 | 6 / 2 | |
| 0.34.9 | 6 / 2 | |
| 0.34.8 | 6 / 2 | |
| 0.34.7 | 6 / 2 | |
| 0.34.6 | 6 / 2 | |
| 0.34.5 | 6 / 2 | |
| 0.34.4 | 6 / 2 | |
| 0.34.3 | 6 / 2 | |
| 0.34.2 | 6 / 2 | |
| 0.34.1 | 6 / 2 | |
| 0.34.0 | 6 / 2 | |
| 0.33.9 | 6 / 2 | |
| 0.33.7 | 6 / 2 | |
| 0.33.6 | 6 / 2 | |
| 0.33.5 | 6 / 2 | |
| 0.33.4 | 6 / 2 | |
| 0.33.3 | 6 / 2 | |
| 0.33.2 | 6 / 2 | |
| 0.33.1 | 6 / 2 | |
| 0.33.0 | 6 / 2 |
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.