@tarojs/cli-convertor
cli tool for taro-convert
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:@tarojs/cli | AI (dependencies): Sibling monorepo package from NervJS/taro; version-locked to same release. | ai | |
| dependencies | unvetted-dep:@tarojs/helper | AI (dependencies): Sibling monorepo package from NervJS/taro; version-locked to same release. | ai | |
| dependencies | unvetted-dep:@tarojs/taroize | AI (dependencies): Sibling monorepo package from NervJS/taro; version-locked to same release. | ai | |
| dependencies | unvetted-dep:@tarojs/transformer-wx | AI (dependencies): Sibling monorepo package from NervJS/taro; version-locked to same release. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): fs-extra is a declared runtime dependency; phantom-dep heuristic fires incorrectly here. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance not yet adopted by NervJS/taro, consistent across all versions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 12 / 6 | |
| 4.1.11 | 12 / 6 | |
| 4.1.10 | 12 / 6 | |
| 4.1.8 | 13 / 5 | |
| 4.1.7 | 13 / 5 | |
| 4.1.6 | 13 / 5 | |
| 4.1.2 | 13 / 5 | |
| 4.1.0 | 13 / 5 | |
| 3.6.39 | 14 / 7 |
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.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.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.
v3.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.