Vulnerability Database · Go · Package report

github.com/gregjones/httpcache: vulnerability history, versions and safety

github.com/gregjones/httpcache 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/gregjones/httpcache v0.0.0-20190611155906-901d90724c79 i

Updated on 23 Oct 2026

Good news: v0.0.0-20190611155906-901d90724c79, the version you would install today, has no known vulnerabilities.

Package health score 57/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Widely used
  • Community Quiet

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

  • Current release v0.0.0-20190611155906-901d90724c79 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 755 i
  • OpenSSF scorecard 2/10 i
  • Last release 88 months ago i
  • Licence MIT 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/gregjones/httpcache, 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-20190611155906-901d90724c79 11 Jun 2019 none MIT — Details →
v0.0.0-20190212212710-3befbb6ad0cc 12 Feb 2019 none MIT — Details →
v0.0.0-20190203031600-7a902570cb17 03 Feb 2019 none MIT — Details →
v0.0.0-20181110185634-c63ab54fda8f 10 Nov 2018 none MIT — Details →
v0.0.0-20180305231024-9cad4c3443a7 05 Mar 2018 none MIT — Details →
v0.0.0-20171119193500-2bcd89a1743f 19 Nov 2017 none MIT — Details →
v0.0.0-20171102012630-22a0b1feae53 02 Nov 2017 none MIT — Details →
v0.0.0-20170926212834-c1f8028e62ad 26 Sep 2017 none MIT — Details →
v0.0.0-20170920190843-316c5e0ff04e 20 Sep 2017 none MIT — Details →
v0.0.0-20170728041850-787624de3eb7 28 Jul 2017 none MIT — Details →
v0.0.0-20170727193703-efb97ba34474 27 Jul 2017 none MIT — Details →
v0.0.0-20170424210139-0d2297f241a3 24 Apr 2017 none MIT — Details →
v0.0.0-20170414220107-29e7c21dc294 14 Apr 2017 none MIT — Details →
v0.0.0-20170211092055-d02018f006d9 11 Feb 2017 none MIT — Details →
v0.0.0-20170205203639-9c8ca9fd8d22 05 Feb 2017 none MIT — Details →
v0.0.0-20160828165248-413781778738 28 Aug 2016 none MIT — Details →
v0.0.0-20160811062753-2aae00e092c5 11 Aug 2016 none MIT — Details →
v0.0.0-20160524185540-16db777d8ebe 24 May 2016 none MIT — Details →
v0.0.0-20160520211333-01b2fc803248 20 May 2016 none MIT — Details →
v0.0.0-20160519070424-37c2ad677bc8 19 May 2016 none MIT — Details →
v0.0.0-20160518085129-81de9c45ae09 18 May 2016 none MIT — Details →
v0.0.0-20160511175519-2f25d9337e9e 11 May 2016 none MIT — Details →
v0.0.0-20160510174016-6088367fb674 10 May 2016 none MIT — Details →
v0.0.0-20160510173146-eb5015094164 10 May 2016 none MIT — Details →
v0.0.0-20160329211651-f99d4c77b09d 29 Mar 2016 none MIT — Details →
v0.0.0-20160313132734-4b02602f71f4 13 Mar 2016 none MIT — Details →
v0.0.0-20160312152544-6f21ebc0cf10 12 Mar 2016 none MIT — Details →
v0.0.0-20160310195733-5b22f64607e2 10 Mar 2016 none MIT — Details →
v0.0.0-20160201074100-41d86b9a9331 01 Feb 2016 none MIT — Details →
v0.0.0-20160201065039-76776b1052f5 01 Feb 2016 none MIT — Details →
v0.0.0-20151025154847-ae1d6feaf2d3 25 Oct 2015 none MIT — Details →
v0.0.0-20151025153745-2cc28a3c6df5 25 Oct 2015 none MIT — Details →
v0.0.0-20150418121710-a2645c9fb8bb 18 Apr 2015 none MIT — Details →
v0.0.0-20150418121651-378d1dfc17b9 18 Apr 2015 none MIT — Details →
v0.0.0-20150418001238-78a5b0062ee7 18 Apr 2015 none MIT — Details →
v0.0.0-20141220105834-4fb00a8eec00 20 Dec 2014 none MIT — Details →
v0.0.0-20141220102309-cb3afe28f656 20 Dec 2014 none MIT — Details →
v0.0.0-20141109204338-6d9d83c3cb47 09 Nov 2014 none MIT — Details →
v0.0.0-20141106040714-6e141ba02fd4 06 Nov 2014 none MIT — Details →
v0.0.0-20141103201421-c4f0acf5bdd1 03 Nov 2014 none MIT — Details →
v0.0.0-20141101194615-43e2c78eccf6 01 Nov 2014 none MIT — Details →
v0.0.0-20140905102841-e3c274495816 05 Sep 2014 none MIT — Details →
v0.0.0-20140721121510-0e0bfdd1946b 21 Jul 2014 none MIT — Details →
v0.0.0-20140630163834-553cabb31c4e 30 Jun 2014 none MIT — Details →
v0.0.0-20140630001132-1ca018e9392d 30 Jun 2014 none MIT — Details →
v0.0.0-20140315114027-1069b76e0882 15 Mar 2014 none MIT — Details →
v0.0.0-20140313213835-35da90b6a8d1 13 Mar 2014 none MIT — Details →
v0.0.0-20140313213714-6c0ccc1a73f4 13 Mar 2014 none MIT — Details →
v0.0.0-20140111153526-650ce2f4951a 11 Jan 2014 none MIT — Details →
v0.0.0-20131228141639-fdaff968edc4 28 Dec 2013 none MIT — Details →
v0.0.0-20131226201042-8c67176a1bb2 26 Dec 2013 none MIT — Details →
v0.0.0-20131219182117-af3e5d30e3b1 19 Dec 2013 none MIT — Details →
v0.0.0-20131217222747-0e8dac32b03b 17 Dec 2013 none MIT — Details →
v0.0.0-20131214211657-b49eafcc8238 14 Dec 2013 none MIT — Details →
v0.0.0-20130914130729-57a4bffde770 14 Sep 2013 none MIT — Details →
v0.0.0-20130913230410-47cc017e7d23 13 Sep 2013 none MIT — Details →
v0.0.0-20130808234951-d6d2242c57d5 08 Aug 2013 none MIT — Details →
v0.0.0-20130808012717-1071b329a560 08 Aug 2013 none MIT — Details →
v0.0.0-20130807011901-ce00995f7ebe 07 Aug 2013 none MIT — Details →
v0.0.0-20130427180221-c6ed3b12499f 27 Apr 2013 none MIT — Details →
v0.0.0-20130411101537-3f32dba33dff 11 Apr 2013 none MIT — Details →
v0.0.0-20130411101218-f8f0402d9bb2 11 Apr 2013 none MIT — Details →
v0.0.0-20130213180251-fcfab8efb780 13 Feb 2013 none MIT — Details →
v0.0.0-20121216163543-110bd421058f 16 Dec 2012 none — — Details →

All 64 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/gregjones/httpcache

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/gregjones/httpcache

Is github.com/gregjones/httpcache safe to use?

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

Vulert scores github.com/gregjones/httpcache 57/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/gregjones/httpcache affected?

No. v0.0.0-20190611155906-901d90724c79, 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/gregjones/httpcache should I use?

v0.0.0-20190611155906-901d90724c79 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/gregjones/httpcache have?

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

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

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