@tarojs/plugin-platform-harmony-ets
OpenHarmony & 鸿蒙系统插件
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/helper | AI (dependencies): Same-org monorepo dependency pinned to matching version; standard Taro release pattern. | ai | |
| dependencies | unvetted-dep:@tarojs/service | AI (dependencies): Same-org monorepo dependency pinned to matching version; standard Taro release pattern. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Active Taro monorepo with frequent releases; maintainer additions are routine for this org-scoped package. | ai | |
| phantom-deps | phantom-dep:webpack | AI (phantom-deps): webpack is a declared runtime dep used via config convention, not direct import; stable for this build-plugin package. | ai | |
| phantom-deps | phantom-dep:@babel/preset-react | AI (phantom-deps): Framework-scoped preset loaded by convention; false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tarojs/runner-utils | AI (phantom-deps): Same-org dep used indirectly; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 4.2.0 | 10 / 7 | |
| 4.1.11 | 10 / 7 | |
| 4.1.10 | 10 / 7 | |
| 4.1.9 | 10 / 7 | |
| 4.1.8 | 10 / 7 | |
| 4.1.7 | 10 / 7 | |
| 4.1.6 | 10 / 7 | |
| 4.1.5 | 10 / 7 | |
| 4.1.4 | 10 / 7 | |
| 4.1.3 | 10 / 7 | |
| 4.1.2 | 10 / 7 | |
| 4.1.1 | 10 / 7 | |
| 4.1.0 | 10 / 7 | |
| 4.0.13 | 10 / 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 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. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
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. 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. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.