@teambit/git
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@teambit/gitconfig | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/harmony | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@teambit/bit-error | AI (dependencies): Internal teambit monorepo dependency; stable pattern across all versions. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established @teambit component package; missing description is a known pattern across their releases. | ai | |
| provenance | no-provenance | AI (provenance): Teambit publishes 1900+ versions without provenance; consistent pattern, not a new risk signal. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @teambit/git is a legitimate Git-integration aspect in the teambit/bit monorepo; not a typosquat of 'got'. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): @teambit/git is a legitimate scoped package; 2-edit distance from 'vite' is coincidental. | ai |
Versions (showing 4 of 407)
| Version | Deps | Published |
|---|---|---|
| 1.0.613 | 7 / 3 | |
| 1.0.612 | 7 / 3 | |
| 1.0.611 | 7 / 3 | |
| 1.0.610 | 7 / 3 |
v1.0.613
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.0.612
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.0.611
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.0.610
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.