VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@xterm/xterm: vulnerability history, versions and safety

@xterm/xterm 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 @xterm/xterm vulnerabilities

Vulert verdict on @xterm/xterm 6.0.0 i

Updated on 23 Oct 2026

Good news: Vulert has no vulnerability on record for @xterm/xterm in the npm ecosystem. That is a good sign, not a guarantee — keep an eye on the versions you run.

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

What to do: Run a supported release and keep monitoring: new vulnerabilities are published for packages every day. Nothing yet: a new vulnerability can appear at any time — Vulert alerts you if one affects this package. Monitor it with Vulert →

  • Current release 6.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,162 packages i
  • Stars 21,278 i
  • OpenSSF scorecard 5/10 i
  • Last release this month 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 @xterm/xterm, 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
6.1.0-beta.315 13 Oct 2026 none MIT — Details →
6.1.0-beta.314 12 Oct 2026 none MIT — Details →
6.1.0-beta.313 12 Oct 2026 none MIT — Details →
6.1.0-beta.312 12 Oct 2026 none MIT — Details →
6.1.0-beta.311 12 Oct 2026 none MIT — Details →
6.1.0-beta.310 12 Oct 2026 none MIT — Details →
6.1.0-beta.309 12 Oct 2026 none MIT — Details →
6.1.0-beta.308 12 Oct 2026 none MIT — Details →
6.1.0-beta.307 12 Oct 2026 none MIT — Details →
6.1.0-beta.306 12 Oct 2026 none MIT — Details →
6.1.0-beta.305 12 Oct 2026 none MIT — Details →
6.1.0-beta.304 30 Aug 2026 none MIT — Details →
6.1.0-beta.303 24 Aug 2026 none MIT — Details →
6.1.0-beta.302 10 Aug 2026 none MIT — Details →
6.1.0-beta.301 10 Aug 2026 none MIT — Details →
6.1.0-beta.300 09 Aug 2026 none MIT — Details →
6.1.0-beta.299 09 Aug 2026 none MIT — Details →
6.1.0-beta.298 09 Aug 2026 none MIT — Details →
6.1.0-beta.297 09 Aug 2026 none MIT — Details →
6.1.0-beta.296 09 Aug 2026 none MIT — Details →
6.1.0-beta.295 09 Aug 2026 none MIT — Details →
6.1.0-beta.294 09 Aug 2026 none MIT — Details →
6.1.0-beta.293 09 Aug 2026 none MIT — Details →
6.1.0-beta.292 27 Jul 2026 none MIT — Details →
6.1.0-beta.291 19 Jul 2026 none MIT — Details →
6.1.0-beta.290 15 Jul 2026 none MIT — Details →
6.1.0-beta.289 13 Jul 2026 none MIT — Details →
6.1.0-beta.288 28 Jun 2026 none MIT — Details →
6.1.0-beta.287 13 Jun 2026 none MIT — Details →
6.1.0-beta.286 13 Jun 2026 none MIT — Details →
6.1.0-beta.285 06 Jun 2026 none MIT — Details →
6.1.0-beta.284 06 Jun 2026 none MIT — Details →
6.1.0-beta.283 06 Jun 2026 none MIT — Details →
6.1.0-beta.282 06 Jun 2026 none MIT — Details →
6.1.0-beta.281 06 Jun 2026 none MIT — Details →
6.1.0-beta.280 06 Jun 2026 none MIT — Details →
6.1.0-beta.279 06 Jun 2026 none MIT — Details →
6.1.0-beta.278 06 Jun 2026 none MIT — Details →
6.1.0-beta.277 06 Jun 2026 none MIT — Details →
6.1.0-beta.276 03 Jun 2026 none MIT — Details →
6.1.0-beta.275 03 Jun 2026 none MIT — Details →
6.1.0-beta.274 02 Jun 2026 none MIT — Details →
6.1.0-beta.273 02 Jun 2026 none MIT — Details →
6.1.0-beta.272 02 Jun 2026 none MIT — Details →
6.1.0-beta.271 02 Jun 2026 none MIT — Details →
6.1.0-beta.270 02 Jun 2026 none MIT — Details →
6.1.0-beta.269 01 Jun 2026 none MIT — Details →
6.1.0-beta.268 01 Jun 2026 none MIT — Details →
6.1.0-beta.267 01 Jun 2026 none MIT — Details →
6.1.0-beta.266 01 Jun 2026 none MIT — Details →
6.1.0-beta.265 01 Jun 2026 none MIT — Details →
6.1.0-beta.264 01 Jun 2026 none MIT — Details →
6.1.0-beta.263 01 Jun 2026 none MIT — Details →
6.1.0-beta.262 01 Jun 2026 none MIT — Details →
6.1.0-beta.261 31 May 2026 none MIT — Details →
6.1.0-beta.260 31 May 2026 none MIT — Details →
6.1.0-beta.259 31 May 2026 none MIT — Details →
6.1.0-beta.258 31 May 2026 none MIT — Details →
6.1.0-beta.257 31 May 2026 none MIT — Details →
6.1.0-beta.256 28 May 2026 none MIT — Details →
6.1.0-beta.255 28 May 2026 none MIT — Details →
6.1.0-beta.254 28 May 2026 none MIT — Details →
6.1.0-beta.253 28 May 2026 none MIT — Details →
6.1.0-beta.252 28 May 2026 none MIT — Details →
6.1.0-beta.251 28 May 2026 none MIT — Details →
6.1.0-beta.250 28 May 2026 none MIT — Details →
6.1.0-beta.249 27 May 2026 none MIT — Details →
6.1.0-beta.248 27 May 2026 none MIT — Details →
6.1.0-beta.247 27 May 2026 none MIT — Details →
6.1.0-beta.246 27 May 2026 none MIT — Details →
6.1.0-beta.245 27 May 2026 none MIT — Details →
6.1.0-beta.244 27 May 2026 none MIT — Details →
6.1.0-beta.243 27 May 2026 none MIT — Details →
6.1.0-beta.242 27 May 2026 none MIT — Details →
6.1.0-beta.241 27 May 2026 none MIT — Details →
6.1.0-beta.240 27 May 2026 none MIT — Details →
6.1.0-beta.239 27 May 2026 none MIT — Details →
6.1.0-beta.238 27 May 2026 none MIT — Details →
6.1.0-beta.237 27 May 2026 none MIT — Details →
6.1.0-beta.236 27 May 2026 none MIT — Details →
6.1.0-beta.235 27 May 2026 none MIT — Details →
6.1.0-beta.234 27 May 2026 none MIT — Details →
6.1.0-beta.233 27 May 2026 none MIT — Details →
6.1.0-beta.232 27 May 2026 none MIT — Details →
6.1.0-beta.231 27 May 2026 none MIT — Details →
6.1.0-beta.230 27 May 2026 none MIT — Details →
6.1.0-beta.229 27 May 2026 none MIT — Details →
6.1.0-beta.228 27 May 2026 none MIT — Details →
6.1.0-beta.227 27 May 2026 none MIT — Details →
6.1.0-beta.226 26 May 2026 none MIT — Details →
6.1.0-beta.225 26 May 2026 none MIT — Details →
6.1.0-beta.224 26 May 2026 none MIT — Details →
6.1.0-beta.223 26 May 2026 none MIT — Details →
6.1.0-beta.222 26 May 2026 none MIT — Details →
6.1.0-beta.221 26 May 2026 none MIT — Details →
6.1.0-beta.220 21 May 2026 none MIT — Details →
6.1.0-beta.219 12 May 2026 none MIT — Details →
6.1.0-beta.218 11 May 2026 none MIT — Details →
6.1.0-beta.217 11 May 2026 none MIT — Details →
6.1.0-beta.216 02 May 2026 none MIT — Details →
6.1.0-beta.215 02 May 2026 none — — Details →
6.1.0-beta.214 01 May 2026 none — — Details →
6.1.0-beta.213 01 May 2026 none — — Details →
6.1.0-beta.212 01 May 2026 none — — Details →
6.1.0-beta.211 01 May 2026 none — — Details →
6.1.0-beta.210 01 May 2026 none — — Details →
6.1.0-beta.209 01 May 2026 none — — Details →
6.1.0-beta.208 01 May 2026 none — — Details →
6.1.0-beta.207 28 Apr 2026 none — — Details →
6.1.0-beta.206 28 Apr 2026 none — — Details →
6.1.0-beta.205 28 Apr 2026 none — — Details →
6.1.0-beta.204 26 Apr 2026 none — — Details →
6.1.0-beta.203 24 Apr 2026 none — — Details →
6.1.0-beta.202 23 Apr 2026 none — — Details →
6.1.0-beta.201 23 Apr 2026 none — — Details →
6.1.0-beta.200 23 Apr 2026 none — — Details →
6.1.0-beta.199 21 Apr 2026 none — — Details →
6.1.0-beta.198 21 Apr 2026 none — — Details →
6.1.0-beta.197 06 Apr 2026 none — — Details →
6.1.0-beta.196 01 Apr 2026 none — — Details →

The newest 120 of 507 versions Vulert tracks. 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 @xterm/xterm

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 @xterm/xterm

Is @xterm/xterm safe to use?

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

Vulert scores @xterm/xterm 90/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).

Which version of @xterm/xterm should I use?

6.0.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 @xterm/xterm have?

0 vulnerabilities are recorded for @xterm/xterm 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 @xterm/xterm vulnerabilities disclosed?

0 vulnerabilities were recorded for @xterm/xterm 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 @xterm/xterm 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 @xterm/xterm for upcoming vulnerabilities?

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