@tarojs/taro-rn
Taro RN framework
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:nullthrows | AI (phantom-deps): React Native utility dep; declared for transitive consumers, not directly imported in this package. | ai | |
| phantom-deps | phantom-dep:babel-preset-expo | AI (phantom-deps): Build/config-level dep for Expo; referenced in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:react-native-stylekit | AI (phantom-deps): Platform-specific binary dep; expected to be declared without direct JS import. | ai | |
| phantom-deps | phantom-dep:react-native-root-toast | AI (phantom-deps): Platform-specific binary dep; expected to be declared without direct JS import. | ai | |
| dependencies | unvetted-dep:@tarojs/runtime-rn | AI (dependencies): Same-monorepo sibling package pinned to matching version; stable pattern across all Taro releases. | ai | |
| provenance | no-provenance | AI (provenance): Large established monorepo; provenance not historically provided across 1050 versions. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 5 / 32 | |
| 4.1.11 | 5 / 32 | |
| 4.1.10 | 5 / 32 | |
| 4.1.9 | 5 / 32 | |
| 4.1.8 | 5 / 32 | |
| 4.1.7 | 5 / 32 | |
| 4.1.6 | 5 / 32 | |
| 4.1.5 | 5 / 32 | |
| 4.1.4 | 5 / 32 | |
| 4.1.3 | 5 / 32 | |
| 4.1.2 | 5 / 33 | |
| 4.1.1 | 5 / 33 | |
| 4.1.0 | 5 / 33 | |
| 4.0.13 | 5 / 33 | |
| 3.6.39 | 28 / 19 |
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
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.
v4.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.13
1 findingPackage 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.