VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

default-gateway: vulnerability history, versions and safety

default-gateway 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 default-gateway vulnerabilities

Vulert verdict on default-gateway 7.2.2 i

Updated on 23 Oct 2026

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

Package health score 56/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

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

  • Current release 7.2.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 761 packages i
  • Stars 90 i
  • OpenSSF scorecard 1/10 i
  • Last release 40 months ago i
  • Licence BSD-2-Clause 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 default-gateway, 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
7.2.2 10 Jun 2023 none BSD-2-Clause — Details →
7.2.1 10 Jun 2023 none BSD-2-Clause — Details →
7.2.0 10 Jun 2023 none BSD-2-Clause — Details →
7.1.0 10 Jun 2023 none BSD-2-Clause — Details →
7.0.0 10 Jun 2023 none BSD-2-Clause — Details →
6.0.3 11 Jan 2021 none BSD-2-Clause — Details →
6.0.2 26 Aug 2020 none BSD-2-Clause — Details →
6.0.1 25 May 2020 none BSD-2-Clause — Details →
6.0.0 11 Mar 2020 none BSD-2-Clause — Details →
5.0.5 14 Nov 2019 none BSD-2-Clause — Details →
5.0.4 15 Oct 2019 none BSD-2-Clause — Details →
5.0.3 14 Aug 2019 none BSD-2-Clause — Details →
5.0.2 14 Jun 2019 none BSD-2-Clause — Details →
5.0.1 14 Jun 2019 none BSD-2-Clause — Details →
5.0.0 14 Jun 2019 none BSD-2-Clause — Details →
4.2.0 06 Mar 2019 none BSD-2-Clause — Details →
4.1.2 25 Feb 2019 none BSD-2-Clause — Details →
4.1.0 25 Feb 2019 none BSD-2-Clause — Details →
4.0.1 23 Feb 2019 none BSD-2-Clause — Details →
4.0.0 22 Feb 2019 none BSD-2-Clause — Details →
3.1.0 15 Feb 2019 none BSD-2-Clause — Details →
3.0.1 05 Sep 2018 none BSD-2-Clause — Details →
3.0.0 23 Aug 2018 none BSD-2-Clause — Details →
2.7.2 31 May 2018 none BSD-2-Clause — Details →
2.7.1 27 Mar 2018 none BSD-2-Clause — Details →
2.7.0 06 Feb 2018 none BSD-2-Clause — Details →
2.6.3 23 Jan 2018 none BSD-2-Clause — Details →
2.6.2 09 Dec 2017 none BSD-2-Clause — Details →
2.6.1 04 Oct 2017 none BSD-2-Clause — Details →
2.6.0 28 Sep 2017 none BSD-2-Clause — Details →
2.5.0 17 Sep 2017 none BSD-2-Clause — Details →
2.4.0 17 Sep 2017 none BSD-2-Clause — Details →
2.3.1 16 Sep 2017 none BSD-2-Clause — Details →
2.3.0 16 Sep 2017 none BSD-2-Clause — Details →
2.2.2 16 Sep 2017 none BSD-2-Clause — Details →
2.2.1 16 Sep 2017 none BSD-2-Clause — Details →
2.2.0 16 Sep 2017 none BSD-2-Clause — Details →
2.1.0 16 Sep 2017 none BSD-2-Clause — Details →
2.0.3 16 Sep 2017 none BSD-2-Clause — Details →
2.0.2 28 Jul 2017 none BSD-2-Clause — Details →
2.0.1 03 Jul 2017 none BSD-2-Clause — Details →
2.0.0 25 Jun 2017 none BSD-2-Clause — Details →
1.0.4 25 Jun 2017 none BSD-2-Clause — Details →
1.0.3 25 Jun 2017 none BSD-2-Clause — Details →
1.0.2 25 Jun 2017 none BSD-2-Clause — Details →
1.0.1 25 Jun 2017 none BSD-2-Clause — Details →
1.0.0 24 Jun 2017 none BSD-2-Clause — Details →
0.8.6 08 Jun 2017 none MIT — Details →
0.8.5 08 Jun 2017 none MIT — Details →
0.8.4 08 Jun 2017 none MIT — Details →
0.8.3 08 Jun 2017 none MIT — Details →
0.8.2 08 Jun 2017 none MIT — Details →
0.8.1 08 Jun 2017 none MIT — Details →
0.8.0 08 Jun 2017 none MIT — Details →

All 54 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 default-gateway

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 default-gateway

Is default-gateway safe to use?

Vulert has no vulnerabilities on record for default-gateway 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 default-gateway's Vulert package health score?

Vulert scores default-gateway 56/100, which reads as usable, but worth attention. 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 default-gateway affected?

No. 7.2.2, 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 default-gateway should I use?

7.2.2 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 default-gateway have?

0 vulnerabilities are recorded for default-gateway 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 default-gateway vulnerabilities disclosed?

0 vulnerabilities were recorded for default-gateway 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 default-gateway 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 default-gateway for upcoming vulnerabilities?

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