VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

got: vulnerability history, versions and safety

got is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 5 releases, first recorded in Jun 2022. 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 got vulnerabilities

Vulert verdict on got 16.1.0 i

Updated on 23 Oct 2026

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

Package health score 86/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 16.1.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 19 Jun 2022 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Depended on by 132 packages i
  • Stars 14,953 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 got, 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
16.1.0 13 Oct 2026 none MIT — Details →
16.0.0 30 Aug 2026 none MIT — Details →
15.1.0 02 Jul 2026 none MIT — Details →
15.0.7 28 Jun 2026 none MIT — Details →
15.0.6 21 Jun 2026 none MIT — Details →
15.0.5 06 May 2026 none MIT — Details →
15.0.4 06 May 2026 none MIT — Details →
15.0.3 21 Apr 2026 none MIT — Details →
15.0.2 13 Apr 2026 none MIT — Details →
15.0.1 08 Apr 2026 none MIT — Details →
15.0.0 01 Apr 2026 none MIT — Details →
14.6.6 30 Dec 2025 none MIT — Details →
14.6.5 22 Nov 2025 none MIT — Details →
14.6.4 14 Nov 2025 none MIT — Details →
14.6.3 07 Nov 2025 none MIT — Details →
14.6.2 02 Nov 2025 none MIT — Details →
14.6.1 25 Oct 2025 none MIT — Details →
14.6.0 16 Oct 2025 none MIT — Details →
14.5.0 10 Oct 2025 none MIT — Details →
14.4.9 17 Sep 2025 none MIT — Details →
14.4.8 30 Aug 2025 none MIT — Details →
14.4.7 31 Mar 2025 none MIT — Details →
14.4.6 10 Feb 2025 none MIT — Details →
14.4.5 23 Nov 2024 none MIT — Details →
14.4.4 04 Nov 2024 none MIT — Details →
14.4.3 09 Oct 2024 none MIT — Details →
14.4.2 24 Jul 2024 none MIT — Details →
14.4.1 06 Jun 2024 none MIT — Details →
14.4.0 04 Jun 2024 none MIT — Details →
14.3.0 18 May 2024 none MIT — Details →
14.2.1 07 Mar 2024 none MIT — Details →
14.2.0 03 Feb 2024 none MIT — Details →
14.1.0 29 Jan 2024 none MIT — Details →
14.0.0 29 Nov 2023 none MIT — Details →
13.0.0 27 May 2023 none MIT — Details →
12.6.1 27 May 2023 none MIT — Details →
12.6.0 03 Mar 2023 none MIT — Details →
11.8.6 08 Dec 2022 none MIT — Details →
12.5.3 16 Nov 2022 none MIT — Details →
12.5.2 12 Oct 2022 none MIT — Details →
12.5.1 27 Sep 2022 none MIT — Details →
12.5.0 19 Sep 2022 none MIT — Details →
12.4.1 02 Sep 2022 none MIT — Details →
12.4.0 02 Sep 2022 none MIT — Details →
12.3.1 06 Aug 2022 none MIT — Details →
12.3.0 28 Jul 2022 none MIT — Details →
12.2.0 24 Jul 2022 none MIT — Details →
12.1.0 25 May 2022 none MIT — Details →
11.8.5 25 May 2022 none MIT — Details →
12.0.4 24 Apr 2022 M1 MIT Yes Details →
12.0.3 26 Mar 2022 M1 MIT Yes Details →
12.0.2 16 Mar 2022 M1 MIT Yes Details →
12.0.1 09 Jan 2022 M1 MIT Yes Details →
12.0.0 10 Dec 2021 M1 MIT Yes Details →
11.8.3 18 Nov 2021 none MIT — Details →
12.0.0-beta.4 12 Aug 2021 none MIT — Details →
12.0.0-beta.3 06 Aug 2021 none MIT — Details →
12.0.0-beta.2 04 Aug 2021 none MIT — Details →
12.0.0-beta.1 22 Jul 2021 none MIT — Details →
11.8.2 26 Feb 2021 none MIT — Details →
11.8.1 10 Dec 2020 none MIT — Details →
11.8.0 20 Oct 2020 none MIT — Details →
11.7.0 18 Sep 2020 none MIT — Details →
11.6.2 10 Sep 2020 none MIT — Details →
11.6.1 08 Sep 2020 none MIT — Details →
11.6.0 02 Sep 2020 none MIT — Details →
11.5.2 07 Aug 2020 none MIT — Details →
11.5.1 16 Jul 2020 none MIT — Details →
11.5.0 07 Jul 2020 none MIT — Details →
11.4.0 04 Jul 2020 none MIT — Details →
11.3.0 05 Jun 2020 none MIT — Details →
11.2.0 01 Jun 2020 none MIT — Details →
11.1.4 16 May 2020 none MIT — Details →
11.1.3 10 May 2020 none MIT — Details →
11.1.2 08 May 2020 none MIT — Details →
11.1.1 06 May 2020 none MIT — Details →
11.1.0 02 May 2020 none MIT — Details →
11.0.3 30 Apr 2020 none MIT — Details →
11.0.2 22 Apr 2020 none MIT — Details →
11.0.1 20 Apr 2020 none MIT — Details →
11.0.0 20 Apr 2020 none MIT — Details →
11.0.0-beta.1 12 Apr 2020 none MIT — Details →
10.7.0 24 Mar 2020 none MIT — Details →
10.6.0 20 Feb 2020 none MIT — Details →
10.5.7 16 Feb 2020 none MIT — Details →
10.5.6 16 Feb 2020 none MIT — Details →
10.5.5 08 Feb 2020 none MIT — Details →
10.5.4 08 Feb 2020 none MIT — Details →
10.5.3 08 Feb 2020 none MIT — Details →
10.5.2 07 Feb 2020 none MIT — Details →
10.5.1 07 Feb 2020 none MIT — Details →
10.5.0 06 Feb 2020 none MIT — Details →
10.4.0 31 Jan 2020 none MIT — Details →
10.3.0 24 Jan 2020 none MIT — Details →
10.2.2 11 Jan 2020 none MIT — Details →
10.2.1 01 Jan 2020 none MIT — Details →
10.2.0 23 Dec 2019 none MIT — Details →
10.1.0 19 Dec 2019 none MIT — Details →
10.0.4 12 Dec 2019 none MIT — Details →
10.0.3 09 Dec 2019 none MIT — Details →
10.0.2 07 Dec 2019 none — — Details →
10.0.1 01 Dec 2019 none — — Details →
10.0.0 01 Dec 2019 none — — Details →
10.0.0-beta.3 01 Dec 2019 none — — Details →
10.0.0-beta.2 25 Nov 2019 none — — Details →
10.0.0-beta.1 18 Nov 2019 none — — Details →
10.0.0-alpha.3.2 01 Nov 2019 none — — Details →
10.0.0-alpha.3.1 01 Nov 2019 none — — Details →
10.0.0-alpha.2.2 24 Sep 2019 none — — Details →
10.0.0-alpha.2.1 23 Sep 2019 none — — Details →
10.0.0-alpha.2 23 Sep 2019 none — — Details →
10.0.0-alpha.1.1 17 Sep 2019 none — — Details →
9.6.0 17 Jan 2019 none — — Details →
9.5.1 13 Jan 2019 none — — Details →
9.5.0 18 Dec 2018 none — — Details →
9.4.0 10 Dec 2018 none — — Details →
9.3.2 08 Nov 2018 none — — Details →
9.3.1 03 Nov 2018 none — — Details →
9.3.0 30 Oct 2018 none — — Details →
9.2.2 17 Sep 2018 none — — Details →

The newest 120 of 202 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 got

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-33987: Vulnerability in got package allows redirect to a UNIX socket 5.3 medium 12.1.0 19 Jun 2022

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 got

Is got safe to use?

Vulert records 1 vulnerabilities for got 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 got's Vulert package health score?

Vulert scores got 86/100, which reads as healthy. 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 got affected?

No. 16.1.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.

How many vulnerabilities does got have?

1 vulnerability is recorded for got 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 got vulnerabilities disclosed?

0 vulnerabilities were recorded for got in the last 12 months, and the oldest entry in this database dates to 19 Jun 2022. 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 got 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 got for upcoming vulnerabilities?

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