VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

puppeteer-extra: vulnerability history, versions and safety

puppeteer-extra 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 puppeteer-extra vulnerabilities

Vulert verdict on puppeteer-extra 3.3.6 i

Updated on 23 Oct 2026

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

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

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

  • Current release 3.3.6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 1,165 packages i
  • Stars 7,411 i
  • OpenSSF scorecard 2/10 i
  • Last release 43 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 puppeteer-extra, 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
3.3.6 01 Mar 2023 none MIT — Details →
3.3.5 01 Mar 2023 none MIT — Details →
3.3.4 07 Jul 2022 none MIT — Details →
3.3.3 07 Jul 2022 none MIT — Details →
3.3.2 07 Jul 2022 none MIT — Details →
3.3.1 06 Jul 2022 none MIT — Details →
3.3.0 20 Jun 2022 none MIT — Details →
3.2.3 28 Sep 2021 none MIT — Details →
3.2.2 25 Sep 2021 none MIT — Details →
3.2.1 23 Sep 2021 none MIT — Details →
3.2.0 21 Sep 2021 none MIT — Details →
3.1.18 14 Mar 2021 none MIT — Details →
3.1.17 15 Feb 2021 none MIT — Details →
3.1.16-next.149 09 Feb 2021 none MIT — Details →
3.1.16-next.126 08 Feb 2021 none MIT — Details →
3.1.16-next.123 08 Feb 2021 none MIT — Details →
3.1.16-next.122 08 Feb 2021 none MIT — Details →
3.1.16-next.121 08 Feb 2021 none MIT — Details →
3.1.16-next.120 08 Feb 2021 none MIT — Details →
3.1.16 13 Jan 2021 none MIT — Details →
3.1.15 18 Aug 2020 none MIT — Details →
3.1.14 18 Aug 2020 none MIT — Details →
3.1.13 23 Jul 2020 none MIT — Details →
3.1.12 09 Jul 2020 none MIT — Details →
3.1.11 08 Jul 2020 none MIT — Details →
3.1.10 08 Jul 2020 none MIT — Details →
3.1.9 06 Jan 2020 none MIT — Details →
3.1.8 05 Jan 2020 none MIT — Details →
3.1.7 03 Dec 2019 none MIT — Details →
3.1.6 03 Dec 2019 none MIT — Details →
3.1.5 01 Dec 2019 none MIT — Details →
3.1.4 29 Nov 2019 none MIT — Details →
3.1.3 29 Nov 2019 none MIT — Details →
3.1.2 29 Nov 2019 none MIT — Details →
2.1.6 25 Nov 2019 none MIT — Details →
2.1.3 12 Feb 2019 none MIT — Details →
2.1.2 11 Feb 2019 none MIT — Details →
2.1.1 10 Sep 2018 none MIT — Details →
2.0.10 18 Aug 2018 none MIT — Details →
2.0.7 07 Jun 2018 none MIT — Details →
2.0.6 06 Jun 2018 none MIT — Details →
2.0.5 02 Jun 2018 none MIT — Details →
2.0.4 02 Jun 2018 none MIT — Details →
2.0.3 01 Jun 2018 none MIT — Details →
2.0.2 01 Jun 2018 none MIT — Details →
2.0.1 29 May 2018 none MIT — Details →
1.1.0 18 May 2018 none MIT — Details →
1.0.1 15 May 2018 none MIT — Details →

All 48 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 puppeteer-extra

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 puppeteer-extra

Is puppeteer-extra safe to use?

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

Vulert scores puppeteer-extra 68/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 puppeteer-extra affected?

No. 3.3.6, 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 puppeteer-extra should I use?

3.3.6 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 puppeteer-extra have?

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

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

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