@tarojs/rn-runner
ReactNative build tool for taro
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:rollup-plugin-image-file | AI (dependencies): Build-tool image plugin used in Rollup pipeline; low risk for this established monorepo package. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; lack of provenance is consistent across all Taro packages. | ai | |
| phantom-deps | phantom-dep:acorn | AI (phantom-deps): Taro monorepo; acorn declared as dep for config/tooling use, stable false positive. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Taro monorepo; lodash declared as dep for config/tooling use, stable false positive. | ai | |
| phantom-deps | phantom-dep:stylelint-config-taro-rn | AI (phantom-deps): Config-only dep referenced in config files; expected pattern for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 15 / 12 | |
| 4.1.10 | 15 / 12 | |
| 4.1.9 | 15 / 12 | |
| 4.1.8 | 15 / 12 | |
| 4.1.7 | 15 / 12 | |
| 4.1.5 | 15 / 12 | |
| 4.1.3 | 15 / 12 | |
| 4.1.1 | 15 / 13 |
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.9
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.