@tarojs/rn-supporter
Taro rn supporter
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:metro-core | AI (phantom-deps): Config-referenced dep in a React Native bundler support package; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:metro-resolver | AI (phantom-deps): Config-referenced dep in a React Native bundler support package; not a direct import by design. | ai | |
| phantom-deps | phantom-dep:babel-plugin-global-define | AI (phantom-deps): Passed as babel plugin config, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:babel-plugin-jsx-attributes-array-to-object | AI (phantom-deps): Passed as babel plugin config, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:babel-plugin-transform-react-jsx-to-rn-stylesheet | AI (phantom-deps): Passed as babel plugin config, not directly imported; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-native-svg-transformer | AI (phantom-deps): Platform-specific transformer referenced in config; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@tarojs/taro | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@tarojs/rn-transformer | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@tarojs/rn-style-transformer | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic is a false positive here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established monorepo sub-package; sparse README and no keywords are expected for internal tooling packages. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 20 / 5 | |
| 4.1.11 | 20 / 5 | |
| 4.1.10 | 20 / 5 | |
| 4.1.9 | 20 / 5 | |
| 4.1.8 | 20 / 5 | |
| 4.1.7 | 20 / 5 | |
| 4.1.6 | 20 / 5 | |
| 4.1.5 | 20 / 5 | |
| 4.1.4 | 20 / 5 | |
| 4.1.3 | 20 / 5 | |
| 4.1.2 | 20 / 6 | |
| 4.1.1 | 20 / 6 | |
| 4.1.0 | 20 / 6 | |
| 4.0.13 | 20 / 6 |
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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.