← Home

@giteeteam/apps-cli

npm

Giteeteam Apps cli

10
Versions
ISC
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

stevencjcyezhimingzhijun714songqythornwu

Keywords

typescriptgiteeteamcli

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): http-proxy-middleware is a legitimate, established dep consistent with the CLI's Express-based dev server functionality. ai
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 10 of 10)

Version Deps Published
2.0.3 27 / 11
2.0.2 27 / 11
2.0.1 27 / 11
2.0.0 27 / 11
1.1.1 26 / 11
1.1.0 26 / 11
1.0.1 26 / 11
1.0.0 26 / 11
0.8.18 34 / 11
0.5.7 21 / 14

v2.0.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.18

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.5.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.