@teambit/gitconfig
1
Versions
—
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
learn-bitteambit-ownershohamgiladdavidfirstlalybarranm8odedreguysaaritaymendelerezbitjoshk2redigmayona007jonisarocombe
Keywords
gitconfig
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Package wraps git config via shell; child_process use is core functionality, not malicious. | ai | |
| semgrep | semgrep:child-process-exec | AI (semgrep): exec() runs git config commands — expected and documented behavior for this package. | ai | |
| phantom-deps | phantom-dep:askconfig | AI (phantom-deps): Declared in package.json as a dependency; phantom-dep heuristic false positive for config-referenced deps. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 2.0.10 | 7 / 8 |
v2.0.10
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.