VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

es-git: vulnerability history, versions and safety

es-git is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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 es-git vulnerabilities

Vulert verdict on es-git 0.7.0 i

Updated on 23 Oct 2026

Good news: 0.7.0, the version you would install today, has no known vulnerabilities.

Package health score 80/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 0.7.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Last release 5 months ago i
  • Licence MIT 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 es-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
0.7.0-next.198 12 Oct 2026 none MIT — Details →
0.7.0-next.197 11 Oct 2026 none MIT — Details →
0.7.0-next.196 11 Oct 2026 none MIT — Details →
0.7.0-next.195 11 Oct 2026 none MIT — Details →
0.7.0-next.194 08 Oct 2026 none MIT — Details →
0.7.0-next.193 08 Sep 2026 none MIT — Details →
0.7.0-next.192 31 Aug 2026 none MIT — Details →
0.7.0-next.191 17 May 2026 none MIT — Details →
0.7.0 17 May 2026 none MIT — Details →
0.7.0-next.190 17 May 2026 none MIT — Details →
0.6.0-next.188 12 May 2026 none MIT — Details →
0.6.0-next.187 12 May 2026 none MIT — Details →
0.6.0-next.186 12 May 2026 none MIT — Details →
0.6.0-next.185 12 May 2026 none MIT — Details →
0.6.0-next.184 10 May 2026 none MIT — Details →
0.6.0-next.183 10 May 2026 none MIT — Details →
0.6.0-next.182 10 May 2026 none MIT — Details →
0.6.0-next.181 10 May 2026 none MIT — Details →
0.6.0-next.180 07 May 2026 none MIT — Details →
0.6.0-next.179 06 Apr 2026 none MIT — Details →
0.6.0-next.178 02 Mar 2026 none MIT — Details →
0.6.0-next.177 02 Mar 2026 none MIT — Details →
0.6.0-next.176 12 Feb 2026 none MIT — Details →
0.6.0-next.175 30 Dec 2025 none MIT — Details →
0.6.0 30 Dec 2025 none MIT — Details →
0.5.0-next.173 28 Dec 2025 none MIT — Details →
0.5.0-next.172 28 Dec 2025 none MIT — Details →
0.5.0-next.171 28 Dec 2025 none MIT — Details →
0.5.0-next.170 27 Dec 2025 none MIT — Details →
0.5.0-next.169 27 Dec 2025 none MIT — Details →
0.5.0-next.168 26 Dec 2025 none MIT — Details →
0.5.0-next.167 26 Dec 2025 none MIT — Details →
0.5.0-next.166 24 Dec 2025 none MIT — Details →
0.5.0-next.165 02 Dec 2025 none MIT — Details →
0.5.0-next.164 30 Nov 2025 none MIT — Details →
0.5.0-next.163 29 Nov 2025 none MIT — Details →
0.5.0-next.162 20 Nov 2025 none MIT — Details →
0.5.0-next.161 20 Nov 2025 none MIT — Details →
0.5.0-next.160 20 Nov 2025 none MIT — Details →
0.5.0-next.159 20 Nov 2025 none MIT — Details →
0.5.0-next.158 20 Nov 2025 none MIT — Details →
0.5.0-next.153 23 Oct 2025 none MIT — Details →
0.4.0-next.151 15 Oct 2025 none MIT — Details →
0.4.0-next.148 10 Oct 2025 none MIT — Details →
0.4.0-next.147 27 Sep 2025 none MIT — Details →
0.4.0-next.146 27 Sep 2025 none MIT — Details →
0.4.0-next.145 25 Sep 2025 none MIT — Details →
0.4.0-next.144 25 Aug 2025 none MIT — Details →
0.4.0-next.143 25 Aug 2025 none MIT — Details →
0.4.0-next.142 24 Aug 2025 none MIT — Details →
0.4.0-next.141 23 Aug 2025 none MIT — Details →
0.4.0-next.140 23 Aug 2025 none MIT — Details →
0.4.0-next.139 23 Aug 2025 none MIT — Details →
0.4.0-next.138 18 Aug 2025 none MIT — Details →
0.4.0-next.137 17 Aug 2025 none MIT — Details →
0.4.0-next.136 08 Aug 2025 none MIT — Details →
0.4.0-next.135 22 Jul 2025 none MIT — Details →
0.4.0-next.134 22 Jun 2025 none MIT — Details →
0.4.0 22 Jun 2025 none MIT — Details →
0.3.0-next.132 19 Jun 2025 none MIT — Details →
0.3.0-next.131 03 Jun 2025 none MIT — Details →
0.3.0-next.130 06 May 2025 none MIT — Details →
0.3.0-next.129 05 May 2025 none MIT — Details →
0.3.0-next.128 05 May 2025 none MIT — Details →
0.3.0-next.127 05 May 2025 none MIT — Details →
0.3.0-next.126 27 Apr 2025 none MIT — Details →
0.3.0 26 Apr 2025 none MIT — Details →
0.3.0-next.124 26 Apr 2025 none MIT — Details →
0.3.0-next.123 26 Apr 2025 none MIT — Details →
0.2.0-next.121 26 Apr 2025 none MIT — Details →
0.2.0-next.120 26 Apr 2025 none MIT — Details →
0.2.0-next.119 26 Apr 2025 none MIT — Details →
0.2.0-next.118 26 Apr 2025 none MIT — Details →
0.2.0-next.117 26 Apr 2025 none MIT — Details →
0.2.0-next.116 20 Apr 2025 none MIT — Details →
0.2.0-next.115 20 Apr 2025 none MIT — Details →
0.2.0-next.114 20 Apr 2025 none MIT — Details →
0.2.0-next.113 19 Apr 2025 none MIT — Details →
0.2.0-next.112 19 Apr 2025 none MIT — Details →
0.2.0-next.111 19 Apr 2025 none MIT — Details →
0.2.0-next.110 14 Apr 2025 none MIT — Details →
0.2.0-next.109 13 Apr 2025 none MIT — Details →
0.2.0-next.108 13 Apr 2025 none MIT — Details →
0.2.0-next.107 13 Apr 2025 none MIT — Details →
0.2.0-next.106 12 Apr 2025 none MIT — Details →
0.2.0-next.105 12 Apr 2025 none MIT — Details →
0.2.0-next.104 09 Apr 2025 none MIT — Details →
0.2.0-next.103 07 Apr 2025 none MIT — Details →
0.2.0 05 Apr 2025 none MIT — Details →
0.2.0-next.102 05 Apr 2025 none MIT — Details →
0.1.0-next.100 05 Apr 2025 none MIT — Details →
0.1.0-next.99 05 Apr 2025 none MIT — Details →
0.1.0 25 Mar 2025 none MIT — Details →
0.0.14 12 Feb 2025 none MIT — Details →
0.0.12 09 Feb 2025 none MIT — Details →
1.0.0-security 07 Feb 2025 none ISC — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for es-git

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 es-git

Is es-git safe to use?

Vulert has no vulnerabilities on record for es-git in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is es-git's Vulert package health score?

Vulert scores es-git 80/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 es-git affected?

No. 0.7.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 es-git should I use?

0.7.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 es-git have?

0 vulnerabilities are recorded for es-git in the npm ecosystem: 0 critical, 0 high, 0 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 es-git vulnerabilities disclosed?

0 vulnerabilities were recorded for es-git in the last 12 months. 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 es-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 es-git for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the es-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.