Vulnerability Database · Go · Package report

github.com/jackc/pglogrepl: vulnerability history, versions and safety

github.com/jackc/pglogrepl is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go 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.

Vulert verdict on github.com/jackc/pglogrepl v0.0.0-20261003132456-662581bb6bb6 i

Updated on 23 Oct 2026

Good news: v0.0.0-20261003132456-662581bb6bb6, the version you would install today, has no known vulnerabilities.

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release v0.0.0-20261003132456-662581bb6bb6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 550 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/jackc/pglogrepl, 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
v0.0.0-20261003132456-662581bb6bb6 03 Oct 2026 none MIT — Details →
v0.0.0-20260824121319-4ae5c490f7ce 24 Aug 2026 none MIT — Details →
v0.0.0-20260401131349-e37c41485510 01 Apr 2026 none MIT — Details →
v0.0.0-20251213150135-2e8d0df862c1 13 Dec 2025 none MIT — Details →
v0.0.0-20251213105809-51c88ac1234c 13 Dec 2025 none MIT — Details →
v0.0.0-20250509230407-a9884f6bd75a 09 May 2025 none MIT — Details →
v0.0.0-20250509225531-09610ece7b86 09 May 2025 none MIT — Details →
v0.0.0-20250331215543-51ad596ee12f 31 Mar 2025 none MIT — Details →
v0.0.0-20250331131207-0759e8ce7f99 31 Mar 2025 none MIT — Details →
v0.0.0-20250325003938-6dfcde87cfc7 25 Mar 2025 none MIT — Details →
v0.0.0-20250324135154-095c5cb40be8 24 Mar 2025 none MIT — Details →
v0.0.0-20250322012620-f1e2b1498ed6 22 Mar 2025 none MIT — Details →
v0.0.0-20250315193731-29dcedd74728 15 Mar 2025 none MIT — Details →
v0.0.0-20240307033717-828fbfe908e9 07 Mar 2024 none MIT — Details →
v0.0.0-20231111135425-1627ab1b5780 11 Nov 2023 none MIT — Details →
v0.0.0-20230826184802-9ed16cb201f6 26 Aug 2023 none MIT — Details →
v0.0.0-20230810221841-163df88bad93 10 Aug 2023 none MIT — Details →
v0.0.0-20230810221841-397b8cd98cbb 10 Aug 2023 none MIT — Details →
v0.0.0-20230810221841-af1f71b7082b 10 Aug 2023 none MIT — Details →
v0.0.0-20230810221841-d0818e1fbef7 10 Aug 2023 none MIT — Details →
v0.0.0-20230728225306-38e8a4e50913 28 Jul 2023 none MIT — Details →
v0.0.0-20230630212501-5fd22a600b50 30 Jun 2023 none MIT — Details →
v0.0.0-20230428004623-0c5b98f52784 28 Apr 2023 none MIT — Details →
v0.0.0-20230428004623-7378606cd1bf 28 Apr 2023 none MIT — Details →
v0.0.0-20230318140337-5ef673a9d169 18 Mar 2023 none MIT — Details →
v0.0.0-20221125161640-1e972958ba03 25 Nov 2022 none MIT — Details →
v0.0.0-20221028002905-994c5de07171 28 Oct 2022 none MIT — Details →
v0.0.0-20221022160330-72eff7fc3c66 22 Oct 2022 none MIT — Details →
v0.0.0-20221022160330-e4b0500f7646 22 Oct 2022 none MIT — Details →
v0.0.0-20220827140821-40536e4ca386 27 Aug 2022 none MIT — Details →
v0.0.0-20220516121607-70a00e46998b 16 May 2022 none MIT — Details →
v0.0.0-20220425134335-3a6db5af9c85 25 Apr 2022 none MIT — Details →
v0.0.0-20220404124741-868295ef800a 04 Apr 2022 none MIT — Details →
v0.0.0-20220319145652-8637871ab657 19 Mar 2022 none MIT — Details →
v0.0.0-20220305000529-420b8467887a 05 Mar 2022 none MIT — Details →
v0.0.0-20211030141007-2b9e46709343 30 Oct 2021 none MIT — Details →
v0.0.0-20210731151948-9f1effd582c4 31 Jul 2021 none MIT — Details →
v0.0.0-20210628224733-3140d41f7881 28 Jun 2021 none MIT — Details →
v0.0.0-20210514235833-4afe73f2b337 14 May 2021 none MIT — Details →
v0.0.0-20210109153808-a78a685a0bff 09 Jan 2021 none MIT — Details →
v0.0.0-20200831220807-35832f1993fb 31 Aug 2020 none MIT — Details →
v0.0.0-20200831220807-9df5679e86c1 31 Aug 2020 none MIT — Details →
v0.0.0-20200309144228-32ec418076b3 09 Mar 2020 none MIT — Details →
v0.0.0-20200108151620-37117db5ead4 08 Jan 2020 none MIT — Details →
v0.0.0-20191119150345-1df4b3e965c3 19 Nov 2019 none MIT — Details →
v0.0.0-20191014210501-cd1251fe56d1 14 Oct 2019 none MIT — Details →
v0.0.0-20190823034529-d3b4630b0348 23 Aug 2019 none — — Details →
v0.0.0-20190820015140-5e7b8c1372dd 20 Aug 2019 none — — 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 github.com/jackc/pglogrepl

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 github.com/jackc/pglogrepl

Is github.com/jackc/pglogrepl safe to use?

Vulert has no vulnerabilities on record for github.com/jackc/pglogrepl in Go 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 github.com/jackc/pglogrepl's Vulert package health score?

Vulert scores github.com/jackc/pglogrepl 78/100, which reads as in good shape. 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 github.com/jackc/pglogrepl affected?

No. v0.0.0-20261003132456-662581bb6bb6, 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 github.com/jackc/pglogrepl should I use?

v0.0.0-20261003132456-662581bb6bb6 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 github.com/jackc/pglogrepl have?

0 vulnerabilities are recorded for github.com/jackc/pglogrepl in the Go 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 github.com/jackc/pglogrepl vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/jackc/pglogrepl 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 github.com/jackc/pglogrepl 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 github.com/jackc/pglogrepl for upcoming vulnerabilities?

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