VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

metro4: vulnerability history, versions and safety

metro4 is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 39 releases, first recorded in Oct 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
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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 metro4 vulnerabilities

Vulert verdict on metro4 5.0.0-rc0 i

Updated on 23 Oct 2026

Careful: 5.0.0-rc0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 45/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Niche
  • Community Moderate

The registry marks the latest release as deprecated, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 5.0.0-rc0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 11 Oct 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 1 i
  • Stars 7,088 i
  • OpenSSF scorecard 3/10 i
  • Last release 30 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 metro4, 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
5.0.0-rc0 21 Apr 2024 M1 MIT No Details →
4.5.12 21 Apr 2024 M1 MIT No Details →
4.5.12-rc19 19 Apr 2024 M1 MIT No Details →
4.5.12-rc18 17 Apr 2024 M1 MIT No Details →
4.5.12-rc17 16 Apr 2024 M1 MIT No Details →
4.5.12-rc16 16 Apr 2024 M1 MIT No Details →
4.5.12-rc15 15 Apr 2024 M1 MIT No Details →
4.5.12-rc14 15 Apr 2024 M1 MIT No Details →
4.5.12-rc13 11 Apr 2024 M1 MIT No Details →
4.5.12-rc12 08 Mar 2024 M1 MIT No Details →
4.5.12-rc11 06 Feb 2024 M1 MIT No Details →
4.5.12-rc10 05 Feb 2024 M1 MIT No Details →
4.5.12-rc9 05 Feb 2024 M1 MIT No Details →
4.5.12-rc8 05 Feb 2024 M1 MIT No Details →
4.5.12-rc7 03 Feb 2024 M1 MIT No Details →
4.5.12-rc6 20 Jan 2024 M1 MIT No Details →
4.5.12-rc5 20 Jan 2024 M1 MIT No Details →
4.5.12-rc4 20 Jan 2024 M1 MIT No Details →
4.5.12-rc3 20 Jan 2024 M1 MIT No Details →
4.5.12-rc2 20 Jan 2024 M1 MIT No Details →
4.5.12-rc1 16 Jan 2024 M1 MIT No Details →
4.5.11-rc3 16 Jan 2024 M1 MIT No Details →
4.5.11-rc2 16 Jan 2024 M1 MIT No Details →
4.5.11-rc1 11 Jan 2024 M1 MIT No Details →
4.5.10 04 Dec 2023 M1 MIT No Details →
4.5.9 19 Nov 2023 M1 MIT No Details →
4.5.8 17 Nov 2023 M1 MIT No Details →
4.5.7 14 Nov 2023 M1 MIT No Details →
4.5.6 14 Nov 2023 M1 MIT No Details →
4.5.5 12 Nov 2023 M1 MIT No Details →
4.5.4 31 Oct 2023 M1 MIT No Details →
4.5.3 28 Oct 2023 M1 MIT No Details →
4.5.2 27 Oct 2023 M1 MIT No Details →
4.5.1 23 Jun 2022 M1 MIT No Details →
4.5.0 01 Aug 2021 M1 MIT No Details →
4.4.3 27 Dec 2020 M1 MIT No Details →
4.4.2 08 Nov 2020 M1 MIT No Details →
4.4.1 19 Oct 2020 M1 GPL-3.0 No Details →
4.4.0 27 Sep 2020 M1 MIT No Details →
4.3.10 12 Jul 2020 none MIT — Details →
4.3.9 02 Jul 2020 none MIT — Details →
4.3.8 21 Jun 2020 none MIT — Details →
4.3.7 17 May 2020 none MIT — Details →
4.3.6 15 Mar 2020 none MIT — Details →
4.3.5 14 Jan 2020 none MIT — Details →
4.3.4 24 Nov 2019 none MIT — Details →
4.3.3 03 Nov 2019 none MIT — Details →
4.3.2 20 Oct 2019 none MIT — Details →
4.3.1 25 Sep 2019 none MIT — Details →
4.3.0 22 Sep 2019 none MIT — Details →
4.2.49 15 Sep 2019 none MIT — Details →
4.2.48 12 Aug 2019 none MIT — Details →
4.2.47 29 Jul 2019 none MIT — Details →
4.2.45 17 Jun 2019 none MIT — Details →
4.2.44 03 Jun 2019 none MIT — Details →
4.2.43 19 May 2019 none MIT — Details →
4.2.42 07 May 2019 none MIT — Details →
4.2.41 27 Apr 2019 none MIT — Details →
4.2.40 13 Apr 2019 none MIT — Details →
4.2.39 17 Mar 2019 none MIT — Details →
4.2.38 04 Mar 2019 none MIT — Details →
4.2.37 21 Feb 2019 none MIT — Details →
4.2.36 10 Feb 2019 none MIT — Details →
4.2.35 03 Feb 2019 none MIT — Details →
4.2.34 04 Jan 2019 none MIT — Details →
4.2.33 01 Jan 2019 none MIT — Details →
4.2.32 31 Dec 2018 none MIT — Details →
4.2.31 16 Dec 2018 none MIT — Details →
4.2.30 25 Nov 2018 none MIT — Details →
4.2.29 18 Nov 2018 none MIT — Details →
4.2.28 11 Nov 2018 none MIT — Details →
4.2.27 04 Nov 2018 none MIT — Details →
4.2.26 21 Oct 2018 none MIT — Details →
4.2.25 14 Oct 2018 none MIT — Details →
4.2.24 30 Sep 2018 none MIT — Details →
4.2.23 23 Sep 2018 none MIT — Details →
4.2.22 16 Sep 2018 none MIT — Details →
4.2.21 09 Sep 2018 none MIT — Details →
4.2.20 03 Sep 2018 none MIT — Details →
4.2.19 26 Aug 2018 none MIT — Details →
4.2.18 12 Aug 2018 none MIT — Details →
4.2.17 05 Aug 2018 none MIT — Details →
4.2.16 01 Aug 2018 none MIT — Details →
4.2.15 26 Jul 2018 none MIT — Details →
4.2.14 12 Jul 2018 none MIT — Details →
4.2.13 12 Jul 2018 none MIT — Details →
4.2.12 11 Jul 2018 none MIT — Details →
4.2.11 09 Jul 2018 none MIT — Details →
4.2.10 01 Jul 2018 none MIT — Details →
4.2.9 24 Jun 2018 none MIT — Details →
4.2.8 12 Jun 2018 none MIT — Details →
4.2.7 20 May 2018 none MIT — Details →
4.2.6 10 May 2018 none MIT — Details →
4.2.5 05 May 2018 none MIT — Details →
4.2.4 03 May 2018 none MIT — Details →
4.2.3 02 May 2018 none MIT — Details →
4.2.2 01 May 2018 none MIT — Details →
4.2.1 01 May 2018 none MIT — Details →
4.2.0 29 Apr 2018 none MIT — Details →
4.1.20 27 Apr 2018 none MIT — Details →
4.1.19 27 Apr 2018 none — — Details →
4.1.18 26 Apr 2018 none — — Details →
4.1.17 23 Apr 2018 none — — Details →
4.1.16 16 Apr 2018 none — — Details →
4.1.15 14 Apr 2018 none — — Details →
4.1.14 13 Apr 2018 none — — Details →
4.1.13 10 Apr 2018 none — — Details →
4.1.12 05 Apr 2018 none — — Details →
4.1.11 02 Apr 2018 none — — Details →
4.1.10 31 Mar 2018 none — — Details →
4.1.9 30 Mar 2018 none — — Details →
4.1.8 29 Mar 2018 none — — Details →
4.1.7 28 Mar 2018 none — — Details →
4.1.6 27 Mar 2018 none — — Details →
4.1.5 24 Mar 2018 none — — Details →
4.1.4 24 Mar 2018 none — — Details →
4.1.3 23 Mar 2018 none — — Details →
4.1.2 20 Mar 2018 none — — Details →
4.1.1 20 Mar 2018 none — — Details →
4.1.0 18 Mar 2018 none — — Details →

The newest 120 of 131 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 metro4

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-41376: Cross-Site Scripting in Metro UI 6.1 medium No fix published 11 Oct 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 metro4

Is metro4 safe to use?

Vulert records 1 vulnerabilities for metro4 in npm: 0 critical, 0 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is metro4's Vulert package health score?

Vulert scores metro4 45/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of metro4 affected?

Yes. 5.0.0-rc0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of metro4 should I use?

5.0.0-rc0 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 metro4 have?

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

0 vulnerabilities were recorded for metro4 in the last 12 months, and the oldest entry in this database dates to 11 Oct 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 metro4 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 metro4 for upcoming vulnerabilities?

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