@giteeteam/apps-team-components
Gitee team components
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:react-overlays | AI (dependencies): react-overlays is a well-known React overlay utility; stable dependency for this UI component library. | ai | |
| dependencies | unvetted-dep:compressed-json | AI (dependencies): compressed-json is a legitimate utility package; no malware indicators, stable use in this package. | ai | |
| provenance | no-provenance | AI (provenance): Established internal component library; lack of provenance is consistent across all 176 versions. | ai | |
| phantom-deps | phantom-dep:classnames | AI (phantom-deps): classnames is a listed runtime dependency; phantom-dep false positive for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.11.16 | 10 / 44 | |
| 1.11.15 | 10 / 44 | |
| 1.11.2 | 10 / 44 | |
| 1.11.1 | 10 / 44 | |
| 1.11.0 | 10 / 44 | |
| 1.10.13 | 10 / 44 | |
| 1.10.10 | 10 / 44 |
v1.11.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.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.
v1.10.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.