VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/PuerkitoBio/rehttp: vulnerability history, versions and safety

github.com/PuerkitoBio/rehttp 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.

See all github.com/PuerkitoBio/rehttp vulnerabilities

Vulert verdict on github.com/PuerkitoBio/rehttp v1.4.0 i

Updated on 23 Oct 2026

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

Package health score 55/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.4.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 223 i
  • OpenSSF scorecard 2/10 i
  • Last release 31 months ago i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 22 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/PuerkitoBio/rehttp, 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-20240302223106-2883214e7913 02 Mar 2024 none BSD-3-Clause — Details →
v1.3.1-0.20240302223106-2883214e7913 02 Mar 2024 none BSD-3-Clause — Details →
v1.4.0 02 Mar 2024 none BSD-3-Clause — Details →
v0.0.0-20231215174310-8f425fd4244d 15 Dec 2023 none BSD-3-Clause — Details →
v1.3.1-0.20231215174310-8f425fd4244d 15 Dec 2023 none BSD-3-Clause — Details →
v0.0.0-20231007162015-987d33055919 07 Oct 2023 none BSD-3-Clause — Details →
v1.2.1-0.20231007162015-987d33055919 07 Oct 2023 none BSD-3-Clause — Details →
v1.3.0 07 Oct 2023 none BSD-3-Clause — Details →
v0.0.0-20230923204449-eda55afd2ab1 23 Sep 2023 none BSD-3-Clause — Details →
v1.2.1-0.20230923204449-eda55afd2ab1 23 Sep 2023 none BSD-3-Clause — Details →
v0.0.0-20230309011634-2f8a88fd4a38 09 Mar 2023 none BSD-3-Clause — Details →
v1.1.1-0.20230309011634-2f8a88fd4a38 09 Mar 2023 none BSD-3-Clause — Details →
v1.2.0 09 Mar 2023 none BSD-3-Clause — Details →
v0.0.0-20210519150727-67bd845012d9 19 May 2021 none BSD-3-Clause — Details →
v1.1.1-0.20210519150727-67bd845012d9 19 May 2021 none BSD-3-Clause — Details →
v1.1.0 19 May 2021 none BSD-3-Clause — Details →
v0.0.0-20190614133133-3acc8749c14f 14 Jun 2019 none BSD-3-Clause — Details →
v1.0.1-0.20190614133133-3acc8749c14f 14 Jun 2019 none BSD-3-Clause — Details →
v0.0.0-20180310210549-11cf6ea5d3e9 10 Mar 2018 none BSD-3-Clause — Details →
v1.0.0 10 Mar 2018 none BSD-3-Clause — Details →
v0.0.0-20170324140114-5989d9566be1 24 Mar 2017 none BSD-3-Clause — Details →
v0.0.0-20160726193325-5ed5671ef959 26 Jul 2016 none BSD-3-Clause — Details →
v0.0.0-20160512122201-0e4cdf8b3b99 12 May 2016 none BSD-3-Clause — Details →
v0.0.0-20160217234720-2a1ed5366e35 17 Feb 2016 none BSD-3-Clause — Details →

All 24 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/PuerkitoBio/rehttp

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/PuerkitoBio/rehttp

Is github.com/PuerkitoBio/rehttp safe to use?

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

Vulert scores github.com/PuerkitoBio/rehttp 55/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 github.com/PuerkitoBio/rehttp affected?

No. v1.4.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 github.com/PuerkitoBio/rehttp should I use?

v1.4.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 github.com/PuerkitoBio/rehttp have?

0 vulnerabilities are recorded for github.com/PuerkitoBio/rehttp 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/PuerkitoBio/rehttp vulnerabilities disclosed?

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

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