Vulnerability Database · npm · Package report

matrix-appservice-irc: vulnerability history, versions and safety

matrix-appservice-irc is a package in the npm ecosystem. Vulert records 9 vulnerabilities for it across 59 releases, from May 2022 to Feb 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H2 M5 L2
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.

Vulert verdict on matrix-appservice-irc 0.36.1 i

Updated on 23 Oct 2026

Action needed: 0.36.1 has 5 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 67/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 0.36.1 — affected i
  • Vulnerabilities on record 9 over 2 years · 0 in the last year i
  • Latest disclosure 25 Feb 2025 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Stars 507 i
  • OpenSSF scorecard 4/10 i
  • Last release 23 months ago i
  • Licence Apache-2.0 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 matrix-appservice-irc, 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.36.1 14 Nov 2024 M3 L2 Apache-2.0 Yes Details →
0.36.0 25 Oct 2022 M3 L2 Apache-2.0 Yes Details →
0.35.1 26 Sep 2022 M4 L2 Apache-2.0 Yes Details →
0.35.0 13 Sep 2022 M4 L2 Apache-2.0 Yes Details →
0.32.1 25 Oct 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.32.0-rc2 15 Oct 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.32.0-rc1 08 Oct 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.31.0 20 Sep 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.30.0 18 Aug 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.30.0-rc1 17 Aug 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.29.0 02 Aug 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.29.0-rc1 21 Jul 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.28.0-rc1 19 Jul 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.27.0 16 Jun 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.27.0-rc3 11 Jun 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.27.0-rc2 10 Jun 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.27.0-rc1 10 Jun 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.26.1 03 Jun 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.26.0 13 May 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.26.0-rc2 10 May 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.26.0-rc1 07 May 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.25.0 16 Mar 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.24.0 12 Feb 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.24.0-rc1 02 Feb 2021 H2 M5 L2 Apache-2.0 Yes Details →
0.23.0 01 Dec 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.23.0-rc1 24 Nov 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.22.0 06 Nov 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.21.0 15 Oct 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.21.0-rc3 13 Oct 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.21.0-rc2 09 Oct 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.21.0-rc1 07 Oct 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.20.3 04 Sep 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.20.1 17 Aug 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.19.0 06 Jul 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.19.0-rc1 26 Jun 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.18.0 26 Jun 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.18.0-rc1 22 Jun 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.17.1 06 May 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.17.0 01 May 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.17.0-rc2 15 Apr 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.17.0-rc1 09 Apr 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.16.0 03 Mar 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.15.2 17 Feb 2020 H2 M5 L2 Apache-2.0 Yes Details →
0.13.0 25 Sep 2019 H2 M5 L2 Apache-2.0 Yes Details →
0.12.0 06 Jun 2019 H2 M5 L2 Apache-2.0 Yes Details →
0.11.2 05 Oct 2018 H2 M5 L2 Apache-2.0 Yes Details →
0.11.1 30 Aug 2018 H2 M5 L2 Apache-2.0 Yes Details →
0.11.0 28 Aug 2018 H2 M5 L2 Apache-2.0 Yes Details →
0.10.1 30 Jul 2018 H2 M5 L2 Apache-2.0 Yes Details →
0.8.0 07 Aug 2017 H2 M5 L2 Apache-2.0 Yes Details →
0.7.2 05 Apr 2017 H2 M5 L2 Apache-2.0 Yes Details →
0.7.1 07 Feb 2017 H2 M5 L2 Apache-2.0 Yes Details →
0.7.0 19 Dec 2016 H2 M5 L2 Apache-2.0 Yes Details →
0.6.0 03 Nov 2016 H2 M5 L2 Apache-2.0 Yes Details →
0.5.0 07 Oct 2016 H2 M5 L2 Apache-2.0 Yes Details →
0.4.0 15 Aug 2016 H2 M5 L2 Apache-2.0 Yes Details →
0.3.1 20 Jul 2016 H2 M5 L2 Apache-2.0 Yes Details →
0.3.0 21 Jun 2016 H2 M5 L2 Apache-2.0 Yes Details →
0.1.0 18 May 2015 H2 M5 L2 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2023 2
  • 2024 2
  • 2025 1

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

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 matrix-appservice-irc

Is matrix-appservice-irc safe to use?

Vulert records 9 vulnerabilities for matrix-appservice-irc in npm: 0 critical, 2 high, 5 medium and 2 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 matrix-appservice-irc's Vulert package health score?

Vulert scores matrix-appservice-irc 67/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 matrix-appservice-irc affected?

Yes. 0.36.1, the version you would install today, has 5 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of matrix-appservice-irc should I use?

0.36.1 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 matrix-appservice-irc have?

9 vulnerabilities are recorded for matrix-appservice-irc in the npm ecosystem: 0 critical, 2 high, 5 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new matrix-appservice-irc vulnerabilities disclosed?

0 vulnerabilities were recorded for matrix-appservice-irc in the last 12 months, and the oldest entry in this database dates to 23 May 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 matrix-appservice-irc 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 matrix-appservice-irc for upcoming vulnerabilities?

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