VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

pg-cursor: vulnerability history, versions and safety

pg-cursor 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 pg-cursor vulnerabilities

Vulert verdict on pg-cursor 2.22.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 2.22.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 740 packages i
  • Stars 13,224 i
  • OpenSSF scorecard 4/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 pg-cursor, 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
2.22.1 30 Sep 2026 none MIT — Details →
2.22.0 08 Aug 2026 none MIT — Details →
2.21.0 19 Jun 2026 none MIT — Details →
2.20.0 18 May 2026 none MIT — Details →
2.19.0 04 Mar 2026 none MIT — Details →
2.18.0 25 Feb 2026 none MIT — Details →
2.17.0 30 Jan 2026 none MIT — Details →
2.16.2 20 Jan 2026 none MIT — Details →
2.16.1 15 Jan 2026 none MIT — Details →
2.16.0 14 Jan 2026 none MIT — Details →
2.15.3 27 Jun 2025 none MIT — Details →
2.15.2 19 Jun 2025 none MIT — Details →
2.15.1 18 Jun 2025 none MIT — Details →
2.15.0 12 May 2025 none MIT — Details →
2.14.6 25 Apr 2025 none MIT — Details →
2.14.5 23 Apr 2025 none MIT — Details →
2.14.2 23 Apr 2025 none MIT — Details →
2.14.1 22 Apr 2025 none MIT — Details →
2.14.0 22 Apr 2025 none MIT — Details →
2.13.2-alpha.1 21 Apr 2025 none MIT — Details →
2.13.2-alpha.0 21 Apr 2025 none MIT — Details →
2.13.1 17 Mar 2025 none MIT — Details →
2.13.0 11 Mar 2025 none MIT — Details →
2.12.3 13 Feb 2025 none MIT — Details →
2.12.2 11 Feb 2025 none MIT — Details →
2.12.1 24 Oct 2024 none MIT — Details →
2.12.0 17 Sep 2024 none MIT — Details →
2.11.0 04 Jun 2024 none MIT — Details →
2.10.6 04 Jun 2024 none MIT — Details →
2.10.5 02 Apr 2024 none MIT — Details →
2.10.4 30 Mar 2024 none MIT — Details →
2.10.3 16 Aug 2023 none MIT — Details →
2.10.2 01 Aug 2023 none MIT — Details →
2.10.1 26 Jun 2023 none MIT — Details →
2.10.0 15 May 2023 none MIT — Details →
2.9.0 06 Mar 2023 none MIT — Details →
2.8.0 27 Jan 2023 none MIT — Details →
2.7.4 23 Aug 2022 none MIT — Details →
2.7.3 04 Feb 2022 none MIT — Details →
2.7.1 27 Jul 2021 none MIT — Details →
2.7.0 27 Jul 2021 none MIT — Details →
2.6.0 13 Apr 2021 none MIT — Details →
2.5.2 30 Nov 2020 none MIT — Details →
2.5.1 13 Nov 2020 none MIT — Details →
2.5.0 10 Nov 2020 none MIT — Details →
2.4.2 26 Oct 2020 none MIT — Details →
2.4.1 08 Oct 2020 none MIT — Details →
2.4.0 04 Oct 2020 none MIT — Details →
2.3.3 26 Aug 2020 none MIT — Details →
2.3.2 18 Aug 2020 none MIT — Details →
2.3.0 09 Jul 2020 none MIT — Details →
2.2.2 07 Jul 2020 none MIT — Details →
2.2.1 15 May 2020 none MIT — Details →
2.2.0 13 May 2020 none MIT — Details →
2.1.11 08 May 2020 none MIT — Details →
2.1.10 22 Apr 2020 none MIT — Details →
2.1.9 09 Apr 2020 none MIT — Details →
2.1.8 09 Apr 2020 none MIT — Details →
2.1.7 30 Mar 2020 none MIT — Details →
2.1.6 20 Feb 2020 none MIT — Details →
2.1.5 30 Jan 2020 none MIT — Details →
2.1.4 29 Jan 2020 none MIT — Details →
2.1.3 10 Jan 2020 none MIT — Details →
2.1.2 29 Dec 2019 none MIT — Details →
2.1.1 28 Dec 2019 none MIT — Details →
2.1.0 27 Dec 2019 none MIT — Details →
2.0.3 26 Dec 2019 none MIT — Details →
2.0.2 18 Dec 2019 none MIT — Details →
2.0.1 30 Oct 2019 none MIT — Details →
2.0.0 08 Jan 2019 none MIT — Details →
1.3.0 06 Aug 2017 none MIT — Details →
1.2.2 05 Aug 2017 none MIT — Details →
1.2.1 05 Aug 2017 none MIT — Details →
1.2.0 16 May 2017 none MIT — Details →
1.1.0 27 Apr 2017 none MIT — Details →
1.0.2 27 Apr 2017 none MIT — Details →
1.0.1 29 Jun 2016 none MIT — Details →
1.0.0 25 Sep 2014 none MIT — Details →
0.2.0 22 May 2014 none MIT — Details →
0.1.3 21 Mar 2014 none MIT — Details →
0.1.2 26 Feb 2014 none MIT — Details →
0.1.1 26 Feb 2014 none MIT — Details →
0.1.0 17 Dec 2013 none MIT — Details →
0.0.1 07 Oct 2013 none MIT — Details →

All 84 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 pg-cursor

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 pg-cursor

Is pg-cursor safe to use?

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

Vulert scores pg-cursor 86/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).

Is the latest version of pg-cursor affected?

No. 2.22.1, 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 pg-cursor should I use?

2.22.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 pg-cursor have?

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

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

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