@tarojs/rn-style-transformer
提供 Taro RN 统一处理样式文件能力
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:@tarojs/helper | AI (dependencies): Sibling package within the Taro monorepo; version-locked to same release, stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): @babel/core is a declared runtime dep used by metro-react-native-babel-transformer; phantom-dep is a false positive here. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): PostCSS plugin loader pattern; resolves user-configured plugin names at runtime — stable and expected for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-taro-rn | AI (phantom-deps): Config-file reference pattern in Taro monorepo; not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:stylelint-config-taro-rn | AI (phantom-deps): Config-file reference pattern in Taro monorepo; not a real phantom dep. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Taro monorepo package; README link dump is a known monorepo doc pattern, not spam. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 16 / 1 | |
| 4.1.11 | 16 / 1 | |
| 4.1.10 | 16 / 1 | |
| 4.1.9 | 16 / 1 | |
| 4.1.8 | 16 / 2 | |
| 4.1.7 | 16 / 2 | |
| 4.1.6 | 16 / 2 | |
| 4.1.5 | 16 / 2 | |
| 4.1.4 | 16 / 2 | |
| 4.1.3 | 16 / 2 | |
| 4.1.2 | 16 / 2 | |
| 4.1.1 | 16 / 2 | |
| 4.1.0 | 16 / 2 | |
| 4.0.13 | 16 / 2 | |
| 3.6.40 | 16 / 6 | |
| 3.6.39 | 16 / 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. 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. 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.