VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@npmcli/git: vulnerability history, versions and safety

@npmcli/git is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 10 releases, first recorded in Aug 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @npmcli/git vulnerabilities

Vulert verdict on @npmcli/git 8.0.0 i

Updated on 22 Oct 2026

Good news: 8.0.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 76/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 8.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 8.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 8.0.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 05 Aug 2021 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 452 packages i
  • Stars 75 i
  • OpenSSF scorecard 4/10 i
  • Last release 5 months ago i
  • Licence ISC i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @npmcli/git, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
8.0.0 19 May 2026 none ISC — Details →
7.0.2 24 Feb 2026 none ISC — Details →
7.0.1 13 Nov 2025 none ISC — Details →
7.0.0 17 Sep 2025 none ISC — Details →
6.0.3 18 Feb 2025 none ISC — Details →
6.0.2 18 Feb 2025 none ISC — Details →
6.0.1 02 Oct 2024 none ISC — Details →
6.0.0 26 Sep 2024 none ISC — Details →
5.0.8 09 Jul 2024 none ISC — Details →
5.0.7 04 May 2024 none ISC — Details →
5.0.6 12 Apr 2024 none ISC — Details →
5.0.5 09 Apr 2024 none ISC — Details →
5.0.4 04 Jan 2024 none ISC — Details →
5.0.3 30 Aug 2023 none ISC — Details →
5.0.2 30 Aug 2023 none ISC — Details →
5.0.1 15 Aug 2023 none ISC — Details →
5.0.0 14 Aug 2023 none ISC — Details →
4.1.0 06 Jun 2023 none ISC — Details →
4.0.4 21 Mar 2023 none ISC — Details →
4.0.3 01 Nov 2022 none ISC — Details →
4.0.2 26 Oct 2022 none ISC — Details →
4.0.1 17 Oct 2022 none ISC — Details →
4.0.0 14 Oct 2022 none ISC — Details →
3.0.2 15 Aug 2022 none ISC — Details →
3.0.1 05 Apr 2022 none ISC — Details →
3.0.0 16 Feb 2022 none ISC — Details →
2.1.0 18 Jun 2021 none ISC — Details →
2.0.9 06 May 2021 none ISC — Details →
2.0.8 15 Apr 2021 none ISC — Details →
2.0.7 13 Apr 2021 M1 ISC Yes Details →
2.0.6 11 Feb 2021 M1 ISC Yes Details →
2.0.5 11 Feb 2021 M1 ISC Yes Details →
2.0.4 01 Sep 2020 M1 ISC Yes Details →
2.0.3 11 Jul 2020 M1 ISC Yes Details →
2.0.2 27 Apr 2020 M1 ISC Yes Details →
2.0.1 10 Mar 2020 M1 ISC Yes Details →
2.0.0 10 Mar 2020 M1 ISC Yes Details →
1.0.1 10 Mar 2020 M1 ISC Yes Details →
1.0.0 09 Mar 2020 M1 ISC Yes Details →

All 39 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @npmcli/git

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Arbitrary Command Injection in @npmcli/git N/A medium 2.0.8 05 Aug 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @npmcli/git

Is @npmcli/git safe to use?

Vulert records 1 vulnerabilities for @npmcli/git in npm: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is @npmcli/git's Vulert package health score?

Vulert scores @npmcli/git 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of @npmcli/git affected?

No. 8.0.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of @npmcli/git should I use?

8.0.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @npmcli/git have?

1 vulnerability is recorded for @npmcli/git in the npm ecosystem: 0 critical, 0 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @npmcli/git vulnerabilities disclosed?

0 vulnerabilities were recorded for @npmcli/git in the last 12 months, and the oldest entry in this database dates to 05 Aug 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @npmcli/git are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor @npmcli/git for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @npmcli/git version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.