@npmcli/git
a util for spawning git from npm CLI contexts
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-bulk-read | AI (semgrep): The env-bulk-read pattern is legitimate here: the code filters process.env to only pass safe/non-GIT_ variables to git subprocesses. This is intentional and safe behavior for this package. | ai | |
| provenance | publisher-changed | AI (provenance): npm CLI team migrated to GitHub Actions publishing with SLSA provenance; this is the new normal for @npmcli packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Routine team roster change within the @npmcli GitHub/npm organization. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine team roster change within the @npmcli GitHub/npm organization. | ai | |
| typosquat | typosquat.levenshtein:got | AI (typosquat): @npmcli/git is the official npm CLI git utility under the @npmcli scope; not a typosquat of 'got'. Short name triggers spurious Levenshtein match. | ai | |
| typosquat | typosquat.levenshtein:vite | AI (typosquat): @npmcli/git is the official npm CLI git utility; not a typosquat of 'vite'. Spurious Levenshtein match on short names. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env into a child git process is the intended and necessary behavior for a git-spawning utility. Standard Node.js subprocess pattern. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 8 / 5 | |
| 7.0.1 | 8 / 5 | |
| 7.0.0 | 8 / 5 | |
| 6.0.3 | 8 / 5 | |
| 6.0.2 | 9 / 5 | |
| 6.0.1 | 9 / 5 | |
| 6.0.0 | 9 / 5 | |
| 5.0.8 | 9 / 5 | |
| 5.0.7 | 8 / 5 | |
| 5.0.6 | 8 / 5 | |
| 5.0.5 | 8 / 5 | |
| 5.0.4 | 8 / 5 | |
| 5.0.3 | 8 / 5 | |
| 5.0.2 | 8 / 5 | |
| 5.0.1 | 8 / 5 | |
| 5.0.0 | 8 / 5 | |
| 4.1.0 | 8 / 5 | |
| 4.0.4 | 8 / 5 | |
| 4.0.3 | 9 / 6 | |
| 4.0.2 | 9 / 6 | |
| 4.0.1 | 9 / 6 | |
| 4.0.0 | 9 / 6 | |
| 3.0.2 | 9 / 6 | |
| 3.0.1 | 9 / 4 | |
| 3.0.0 | 9 / 4 | |
| 2.1.0 | 8 / 3 | |
| 2.0.9 | 8 / 3 | |
| 2.0.8 | 8 / 3 |
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.1
2 findingsSpreading entire process.env into an object — may capture all secrets Source: https://github.com/npm/git/blob/6dc0aefb44b66c9f2f941c5182dabbe549bb703b/lib/opts.js#L53 51 | ...opts, 52 | shell: false, > 53 | env: opts.env || { ...finalGitEnv, ...process.env }, 54 | }) 55 |
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.0
2 findingsThis version was published by a different npm account than previous versions on 2025-09-17. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.0
2 findingsPackage name '@npmcli/git' is 1 edit(s) away from popular package 'got'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
2 findingsPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-06-06. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.4
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gar.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-03-21. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-01. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-10-26. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-10-17. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-15. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-05. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.