@arkts/language-plugin
ArkTS Volar Language Plugin.
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:ts-macro | AI (dependencies): ts-macro is a contextually appropriate dep for a Volar/TypeScript language plugin; no malicious indicators. | ai | |
| provenance | no-provenance | AI (provenance): Absence of Sigstore provenance is common (~88% of npm); no other risk signals present. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.3.10 | 4 / 0 | |
| 1.2.8 | 3 / 0 | |
| 1.1.1 | 4 / 0 | |
| 1.1.0 | 4 / 0 | |
| 1.0.6 | 3 / 0 | |
| 1.0.5 | 3 / 0 | |
| 1.0.4 | 3 / 0 | |
| 1.0.0 | 3 / 0 |
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
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.6
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.