@xiao-ying/miniapp-ui-pro
Business-oriented UI components for XiaoYing miniapps, built on @xiao-ying/miniapp-ui.
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Proprietary internal UI library; missing repo/keywords and inflated semver are expected for this org's packages. | ai | |
| provenance | no-provenance | AI (provenance): Proprietary org package; lack of Sigstore provenance is consistent across all versions and not a security risk here. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.2.3 | 8 / 11 | |
| 1.2.2 | 8 / 11 | |
| 1.2.1 | 8 / 11 | |
| 1.2.0 | 7 / 11 | |
| 1.1.1 | 4 / 11 | |
| 1.1.0 | 1 / 9 |
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.