@uni_toolkit/webpack-plugin-component-config
一个用于 UniApp 项目的 Webpack 插件，用于处理 Vue 文件中的 `<component-config>` 标签，将配置提取并合并到对应的 `小程序 JSON 文件` 中。
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:@dcloudio/uni-cli-shared | AI (dependencies): Official DCloud uni-app CLI shared lib; alpha version pinning is normal for uni-app ecosystem tooling. | ai | |
| phantom-deps | phantom-dep:lodash-es | AI (phantom-deps): lodash-es is explicitly declared in dependencies; phantom-dep is a false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Absence of provenance is common (~88% of npm packages); no other risk signals present. | ai | |
| phantom-deps | phantom-dep:rattail | AI (phantom-deps): rattail is declared as a runtime dependency in package.json; phantom-dep heuristic fires because it's not directly imported in source code. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.1.1 | 5 / 4 | |
| 0.1.0 | 5 / 4 | |
| 0.0.20 | 5 / 5 | |
| 0.0.15 | 5 / 5 | |
| 0.0.13 | 5 / 5 | |
| 0.0.12 | 5 / 5 | |
| 0.0.11 | 5 / 5 | |
| 0.0.10 | 5 / 5 | |
| 0.0.6 | 5 / 5 | |
| 0.0.5 | 5 / 5 | |
| 0.0.2 | 4 / 4 | |
| 0.0.1 | 4 / 4 |
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.