Vulnerability Database · Go · Package report

github.com/pquerna/cachecontrol: vulnerability history, versions and safety

github.com/pquerna/cachecontrol 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/pquerna/cachecontrol v0.2.0 i

Updated on 23 Oct 2026

Good news: v0.2.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 v0.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.2.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 150 i
  • OpenSSF scorecard 2/10 i
  • Last release 42 months ago i
  • Licence Apache-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 github.com/pquerna/cachecontrol, 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.2.1-0.20260319221038-ff73c64d4b12 19 Mar 2026 none Apache-2.0 — Details →
v0.0.0-20240709150119-0a96b57e205c 09 Jul 2024 none Apache-2.0 — Details →
v0.2.1-0.20240709150119-0a96b57e205c 09 Jul 2024 none Apache-2.0 — Details →
v0.2.1-0.20240703174233-1a9788d44b89 03 Jul 2024 none Apache-2.0 — Details →
v0.2.1-0.20240701143629-e21f94d168c4 01 Jul 2024 none Apache-2.0 — Details →
v0.0.0-20230415224848-baaf0ee61529 15 Apr 2023 none Apache-2.0 — Details →
v0.1.1-0.20230415224848-baaf0ee61529 15 Apr 2023 none Apache-2.0 — Details →
v0.2.0 15 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20230415153852-792e5eae3205 15 Apr 2023 none Apache-2.0 — Details →
v0.1.1-0.20230415153852-792e5eae3205 15 Apr 2023 none Apache-2.0 — Details →
v0.0.0-20210401182836-348dae40445e 01 Apr 2021 none Apache-2.0 — Details →
v0.1.1-0.20210401182836-348dae40445e 01 Apr 2021 none Apache-2.0 — Details →
v0.1.0 01 Apr 2021 none Apache-2.0 — Details →
v0.0.0-20210401181621-172bcf0218ae 01 Apr 2021 none Apache-2.0 — Details →
v0.0.0-20201207185200-18e48a502102 07 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201205024021-ac21108117ac 05 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201106152158-0091f4817a1f 06 Nov 2020 none Apache-2.0 — Details →
v0.0.0-20200922133218-9d236a72f6d5 22 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20200921180117-858c6e7e6b7e 21 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20200920212527-23aa5369f7e8 20 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20200819021114-67c6ae64274f 19 Aug 2020 none Apache-2.0 — Details →
v0.0.0-20200818163247-d6739d4cc238 18 Aug 2020 none Apache-2.0 — Details →
v0.0.0-20200818124838-2341a9d23655 18 Aug 2020 none Apache-2.0 — Details →
v0.0.0-20190905161545-36aa3f513bfe 05 Sep 2019 none Apache-2.0 — Details →
v0.0.0-20180517163645-1555304b9b35 17 May 2018 none Apache-2.0 — Details →
v0.0.0-20180517162554-0923c70de240 17 May 2018 none Apache-2.0 — Details →
v0.0.0-20180503211057-fd225a25f198 03 May 2018 none Apache-2.0 — Details →
v0.0.0-20180403232221-dcf694c2694d 03 Apr 2018 none Apache-2.0 — Details →
v0.0.0-20180306154005-525d0eb5f91d 06 Mar 2018 none Apache-2.0 — Details →
v0.0.0-20171018203845-0dec1b30a021 18 Oct 2017 none Apache-2.0 — Details →
v0.0.0-20170706045224-5475d973ea70 06 Jul 2017 none Apache-2.0 — Details →
v0.0.0-20170629161721-b548e17eed4d 29 Jun 2017 none Apache-2.0 — Details →
v0.0.0-20170329165416-9299cc36e57c 29 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20170329165350-25a9468c7ff5 29 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20170328151714-2c3410a7c1ba 28 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20160421231612-c97913dcbd76 21 Apr 2016 none Apache-2.0 — Details →
v0.0.0-20160421225514-a4a7334f1588 21 Apr 2016 none Apache-2.0 — Details →
v0.0.0-20150403001439-2accf071192f 03 Apr 2015 none Apache-2.0 — Details →
v0.0.0-20150402215541-0fdff3a3e23d 02 Apr 2015 none Apache-2.0 — Details →
v0.0.0-20150401142940-7ec85781f3d7 01 Apr 2015 none Apache-2.0 — Details →
v0.0.0-20150331235702-04ed7243c064 31 Mar 2015 none Apache-2.0 — Details →
v0.0.0-20150330234848-6af64f3e7bda 30 Mar 2015 none Apache-2.0 — Details →

All 42 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/pquerna/cachecontrol

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/pquerna/cachecontrol

Is github.com/pquerna/cachecontrol safe to use?

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

Vulert scores github.com/pquerna/cachecontrol 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/pquerna/cachecontrol affected?

No. v0.2.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/pquerna/cachecontrol should I use?

v0.2.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/pquerna/cachecontrol have?

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

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

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