@glodon-aiot/react-biz-components
[git 使用文档](./README.git.md) | 组件库使用文档
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:style-loader | AI (phantom-deps): Referenced in build config only, not a runtime import; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:framer-motion | AI (phantom-deps): Referenced in config files only; stable false positive for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.17.0 | 10 / 43 | |
| 3.16.0 | 10 / 43 | |
| 3.15.0 | 10 / 43 | |
| 3.11.1 | 10 / 43 | |
| 3.9.1 | 10 / 43 | |
| 3.9.0 | 10 / 43 | |
| 3.8.0 | 10 / 43 | |
| 3.6.2 | 10 / 43 |
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.