Vulnerability Database · Go · Package report

pgregory.net/rapid: vulnerability history, versions and safety

pgregory.net/rapid 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 pgregory.net/rapid v1.3.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release v1.3.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 902 i
  • OpenSSF scorecard 3/10 i
  • Last release 6 months ago i
  • Licence MPL-2.0 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 pgregory.net/rapid, 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
v1.3.1-0.20260904084459-6706a6fd8373 04 Sep 2026 none MPL-2.0 — Details →
v1.2.1-0.20260330155616-9bafe0734374 30 Mar 2026 none MPL-2.0 — Details →
v1.3.0 30 Mar 2026 none MPL-2.0 — Details →
v1.2.1-0.20260127110422-2f95a47c539f 27 Jan 2026 none MPL-2.0 — Details →
v1.2.1-0.20260110120811-b9c78bfdd0d3 10 Jan 2026 none MPL-2.0 — Details →
v1.2.1-0.20260107201848-5ae52d8cd7ee 07 Jan 2026 none MPL-2.0 — Details →
v1.2.1-0.20251017070445-6be41f8ea26f 17 Oct 2025 none MPL-2.0 — Details →
v1.2.1-0.20251016141531-882162050472 16 Oct 2025 none MPL-2.0 — Details →
v1.2.0 24 Feb 2025 none MPL-2.0 — Details →
v1.1.1-0.20250220065734-c3c5e3cee4e8 20 Feb 2025 none MPL-2.0 — Details →
v1.1.1-0.20241105130958-4b9330502c6f 05 Nov 2024 none MPL-2.0 — Details →
v1.1.1-0.20240727055421-ee28b02bc175 27 Jul 2024 none MPL-2.0 — Details →
v1.1.1-0.20240606091758-3aa554aaca7a 06 Jun 2024 none MPL-2.0 — Details →
v1.1.1-0.20240512154654-654675a3db07 12 May 2024 none MPL-2.0 — Details →
v1.1.1-0.20240401182707-34cb5b24e44b 01 Apr 2024 none MPL-2.0 — Details →
v0.0.0-20231104075452-d56e0371c298 04 Nov 2023 none MPL-2.0 — Details →
v1.1.1-0.20231104075452-d56e0371c298 04 Nov 2023 none MPL-2.0 — Details →
v1.1.1-0.20230808194308-efc31a7e25c4 08 Aug 2023 none MPL-2.0 — Details →
v1.1.0 08 Aug 2023 none MPL-2.0 — Details →
v1.0.2-0.20230803221110-f4756c7c7191 03 Aug 2023 none MPL-2.0 — Details →
v1.0.1 03 Aug 2023 none MPL-2.0 — Details →
v1.0.1-0.20230704221416-d59a3887beba 04 Jul 2023 none MPL-2.0 — Details →
v1.0.1-0.20230613055607-0489b8cc85e9 13 Jun 2023 none MPL-2.0 — Details →
v1.0.0 12 Jun 2023 none MPL-2.0 — Details →
v0.7.2 12 Jun 2023 none MPL-2.0 — Details →
v0.7.1 11 Jun 2023 none MPL-2.0 — Details →
v0.7.1-0.20230611202741-3f13c8a26682 11 Jun 2023 none MPL-2.0 — Details →
v0.7.0 10 Jun 2023 none MPL-2.0 — Details →
v0.6.2 03 Jun 2023 none MPL-2.0 — Details →
v0.6.1 31 May 2023 none MPL-2.0 — Details →
v0.5.8-0.20230511174411-95d7a399e3d0 11 May 2023 none MPL-2.0 — Details →
v0.6.0 11 May 2023 none MPL-2.0 — Details →
v0.5.8-0.20230429160132-69db632130f5 29 Apr 2023 none MPL-2.0 — Details →
v0.5.7 27 Apr 2023 none MPL-2.0 — Details →
v0.5.6 27 Apr 2023 none MPL-2.0 — Details →
v0.5.6-0.20230208200748-b5610200ba39 08 Feb 2023 none MPL-2.0 — Details →
v0.5.5 08 Jan 2023 none MPL-2.0 — Details →
v0.5.4 08 Jan 2023 none MPL-2.0 — Details →
v0.5.3 16 Sep 2022 none MPL-2.0 — Details →
v0.5.3-0.20220829182140-412942d7e5e7 29 Aug 2022 none MPL-2.0 — Details →
v0.5.2 29 Aug 2022 none MPL-2.0 — Details →
v0.5.1 29 Aug 2022 none MPL-2.0 — Details →
v0.5.0 29 Aug 2022 none MPL-2.0 — Details →
v0.4.9-0.20220824180520-ff836af2b002 24 Aug 2022 none MPL-2.0 — Details →
v0.4.8 14 Jul 2022 none MPL-2.0 — Details →
v0.4.8-0.20220407201100-5408033e60bd 07 Apr 2022 none MPL-2.0 — Details →
v0.4.8-0.20210914175237-dd3e976d4df3 14 Sep 2021 none MPL-2.0 — Details →
v0.4.8-0.20210909203332-a0267553f206 09 Sep 2021 none MPL-2.0 — Details →
v0.4.8-0.20210818194349-32f9d9b0a812 18 Aug 2021 none MPL-2.0 — Details →
v0.4.8-0.20210720111545-ef97f657bb33 20 Jul 2021 none MPL-2.0 — Details →
v0.4.7 05 Jul 2021 none MPL-2.0 — Details →
v0.4.6 08 Apr 2021 none MPL-2.0 — Details →
v0.4.5 18 Feb 2021 none MPL-2.0 — Details →
v0.4.4 26 Dec 2020 none MPL-2.0 — Details →
v0.4.3 23 Dec 2020 none MPL-2.0 — Details →
v0.4.2 08 Nov 2020 none MPL-2.0 — Details →
v0.4.1 02 Sep 2020 none MPL-2.0 — Details →
v0.4.1-0.20200715105708-a7a2b0134cf9 15 Jul 2020 none MPL-2.0 — Details →
v0.4.0 01 Jul 2020 none MPL-2.0 — Details →
v0.3.9 05 Jun 2020 none MPL-2.0 — Details →
v0.3.8 15 May 2020 none MPL-2.0 — Details →
v0.3.7 11 May 2020 none MPL-2.0 — Details →
v0.3.6 11 May 2020 none MPL-2.0 — Details →
v0.3.5 04 May 2020 none MPL-2.0 — Details →
v0.3.4 03 May 2020 none MPL-2.0 — Details →
v0.3.3 06 Mar 2020 none MPL-2.0 — Details →
v0.3.2 09 Feb 2020 none MPL-2.0 — Details →
v0.3.1 24 Jan 2020 none MPL-2.0 — Details →
v0.3.0 18 Jan 2020 none MPL-2.0 — Details →

All 69 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 pgregory.net/rapid

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 pgregory.net/rapid

Is pgregory.net/rapid safe to use?

Vulert has no vulnerabilities on record for pgregory.net/rapid 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 pgregory.net/rapid's Vulert package health score?

Vulert scores pgregory.net/rapid 75/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 pgregory.net/rapid affected?

No. v1.3.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 pgregory.net/rapid should I use?

v1.3.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 pgregory.net/rapid have?

0 vulnerabilities are recorded for pgregory.net/rapid 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 pgregory.net/rapid vulnerabilities disclosed?

0 vulnerabilities were recorded for pgregory.net/rapid 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 pgregory.net/rapid 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 pgregory.net/rapid for upcoming vulnerabilities?

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