VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

pegjs: vulnerability history, versions and safety

pegjs 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 pegjs vulnerabilities

Vulert verdict on pegjs 0.10.0 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 0.10.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 3,115 packages i
  • Stars 4,904 i
  • OpenSSF scorecard 2/10 i
  • Last release 122 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 pegjs, 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.11.0-master.b7b87ea 16 Nov 2019 none MIT — Details →
0.11.0-master.9360abb 29 Sep 2019 none MIT — Details →
0.11.0-master.0b102d2 24 Jul 2019 none MIT — Details →
0.11.0-master.30f3260 20 Mar 2019 none MIT — Details →
0.11.0-master.85dbe5a 19 Feb 2019 none MIT — Details →
0.11.0-master.53b9662 15 Feb 2019 none MIT — Details →
0.11.0-master.e829945 15 Feb 2019 none MIT — Details →
0.11.0-master.f69239d 15 Feb 2019 none MIT — Details →
0.11.0-dev.325 18 Sep 2018 none MIT — Details →
0.11.0-dev.273 23 Mar 2018 none MIT — Details →
0.11.0-dev.225 18 Jan 2018 none MIT — Details →
0.11.0-dev.224 18 Jan 2018 none MIT — Details →
0.11.0-dev.200 28 Dec 2017 none MIT — Details →
0.11.0-dev.187 18 Dec 2017 none MIT — Details →
0.10.0 19 Aug 2016 none MIT — Details →
0.9.0 30 Aug 2015 none MIT — Details →
0.8.0 24 Dec 2013 none MIT — Details →
0.7.0 18 Apr 2012 none MIT — Details →
0.6.2 20 Aug 2011 none MIT — Details →
0.6.1 14 Apr 2011 none MIT — Details →
0.6.0 14 Apr 2011 none MIT — Details →

All 21 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 pegjs

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 pegjs

Is pegjs safe to use?

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

Vulert scores pegjs 60/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 pegjs affected?

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

Which version of pegjs should I use?

0.10.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 pegjs have?

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

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

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