@tarojs/vite-runner
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:html-minifier | AI (dependencies): html-minifier is a well-known, stable utility; its use in a vite runner for HTML processing is expected and benign. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Taro monorepo package; sparse metadata is a consistent pattern across all @tarojs/* packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with @tarojs monorepo publishing style; not indicative of malicious intent. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 34 / 10 | |
| 4.1.10 | 34 / 10 | |
| 4.1.8 | 34 / 10 | |
| 4.1.7 | 34 / 10 | |
| 4.1.4 | 34 / 10 | |
| 4.1.0 | 34 / 10 |
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.