@giteeteam/apps-cli
Giteeteam Apps cli
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with 108 versions; lack of provenance is common and not a risk signal here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): 108-version, 1368-day-old org CLI tool; poor README quality is a style issue, not a spam/malware indicator. | ai | |
| dependencies | unvetted-dep:@giteeteam/apps-manifest | AI (dependencies): Scoped sibling package from same @giteeteam org; expected internal dependency. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.0.1 | 26 / 11 | |
| 1.0.0 | 26 / 11 | |
| 0.8.18 | 34 / 11 | |
| 0.5.7 | 21 / 14 |
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.