Vulnerability Database · Go · Package report
github.com/NYTimes/gziphandler: vulnerability history, versions and safety
github.com/NYTimes/gziphandler is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/NYTimes/gziphandler v1.1.1 i
Updated on 23 Oct 2026
Good news: v1.1.1, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Moderate
What to do: Stay on v1.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 893 i
- Last release 92 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/NYTimes/gziphandler, 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.
- v1.1.2-0.20210429195955-5e0908103dcd 29 Apr 2021
- v0.0.0-20191113155120-2f8bb1d30d9d 13 Nov 2019
- v1.1.2-0.20191113155120-2f8bb1d30d9d 13 Nov 2019
- v0.0.0-20190221231647-dd0439581c76 21 Feb 2019
- v1.1.1 21 Feb 2019
- v0.0.0-20190211224723-b8a1976e622c 11 Feb 2019
- v1.1.0 11 Feb 2019
- v1.0.2-0.20190211200303-ae3e73afdc32 11 Feb 2019
- v0.0.0-20180820182813-253f1acb9d9f 20 Aug 2018
- v1.0.2-0.20180820182813-253f1acb9d9f 20 Aug 2018
- v1.0.2-0.20180816200159-edf8477e0cb3 16 Aug 2018
- v0.0.0-20180814212938-448416739b9c 14 Aug 2018
- v1.0.2-0.20180814212938-448416739b9c 14 Aug 2018
- v1.0.2-0.20180814212752-c551b6c3b4b9 14 Aug 2018
- v0.0.0-20180227021810-5032c8878b9d 27 Feb 2018
- v1.0.2-0.20180227021810-5032c8878b9d 27 Feb 2018
- v0.0.0-20180221000450-2600fb119af9 21 Feb 2018
- v1.0.1 21 Feb 2018
- v1.0.1-0.20180221000450-a4fca32d9077 21 Feb 2018
- v0.0.0-20180125165240-289a3b81f5ae 25 Jan 2018
- v1.0.1-0.20180125165240-289a3b81f5ae 25 Jan 2018
- v0.0.0-20180104163112-47ca22a0aeea 04 Jan 2018
- v1.0.1-0.20180104163112-063b218545f6 04 Jan 2018
- v1.0.1-0.20180104163112-47ca22a0aeea 04 Jan 2018
- v0.0.0-20171120163856-d6f46609c762 20 Nov 2017
- v1.0.0 20 Nov 2017
- v0.0.0-20171109155304-843330b8a375 09 Nov 2017
- v0.0.0-20171108202339-0f67f3f25d3b 08 Nov 2017
- v0.0.0-20170916004738-97ae7fbaf816 16 Sep 2017
- v0.0.0-20170915231142-00f646270dcc 15 Sep 2017
- v0.0.0-20170901160716-46766160161f 01 Sep 2017
- v0.0.0-20170824153819-d8cb2618e18c 24 Aug 2017
- v0.0.0-20170804200234-967539e5e271 04 Aug 2017
- v0.0.0-20170623195520-56545f4a5d46 23 Jun 2017
- v0.0.0-20170403152807-22d4470af89e 03 Apr 2017
- v0.0.0-20170329143812-99d30f5e890f 29 Mar 2017
- v0.0.0-20170327175638-d8206bba2a60 27 Mar 2017
- v0.0.0-20170314161103-3b0c4852c5b9 14 Mar 2017
- v0.0.0-20170307160619-fb3533722e14 07 Mar 2017
- v0.0.0-20170305211304-bdb2763a34ed 05 Mar 2017
- v0.0.0-20170104155701-6710af535839 04 Jan 2017
- v0.0.0-20161024143521-172fbbbb329c 24 Oct 2016
- v0.0.0-20160921214618-f6438dbf4a82 21 Sep 2016
- v0.0.0-20160921150601-2e502a45fe06 21 Sep 2016
- v0.0.0-20160920213714-29e02cf5c010 20 Sep 2016
- v0.0.0-20160920205250-2244ea3a1762 20 Sep 2016
- v0.0.0-20160916091501-ec062a4c25bd 16 Sep 2016
- v0.0.0-20160913222309-29d63890a890 13 Sep 2016
- v0.0.0-20160903190603-c24abeb32821 03 Sep 2016
- v0.0.0-20160901134852-d3d7d6775a25 01 Sep 2016
- v0.0.0-20160801152227-44afc598a09b 01 Aug 2016
- v0.0.0-20160419202541-63027b26b87e 19 Apr 2016
- v0.0.0-20160419182243-25fe626c2c78 19 Apr 2016
- v0.0.0-20160415021708-80044e0f3d43 15 Apr 2016
- v0.0.0-20160208015208-a88790d49798 08 Feb 2016
- v0.0.0-20160107103823-763cd3856257 07 Jan 2016
- v0.0.0-20151221171123-92482fb7a26c 21 Dec 2015
- v0.0.0-20150924171255-185f9df07e0c 24 Sep 2015
- v0.0.0-20150923221646-9939d5d76991 23 Sep 2015
- v0.0.0-20150830204901-d0f3df7552af 30 Aug 2015
- v0.0.0-20150818094646-8569b14bad3e 18 Aug 2015
- v0.0.0-20150817180439-85a3cc491e06 17 Aug 2015
- v0.0.0-20150815232238-bdda4e9e87d2 15 Aug 2015
- v0.0.0-20150123190152-05ffaf97c37e 23 Jan 2015
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/NYTimes/gziphandler
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
Questions
About github.com/NYTimes/gziphandler
Is github.com/NYTimes/gziphandler safe to use?
Vulert has no vulnerabilities on record for github.com/NYTimes/gziphandler 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/NYTimes/gziphandler's Vulert package health score?
Vulert scores github.com/NYTimes/gziphandler 69/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/NYTimes/gziphandler affected?
No. v1.1.1, 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/NYTimes/gziphandler should I use?
v1.1.1 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/NYTimes/gziphandler have?
0 vulnerabilities are recorded for github.com/NYTimes/gziphandler 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/NYTimes/gziphandler vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/NYTimes/gziphandler 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/NYTimes/gziphandler 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/NYTimes/gziphandler for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/NYTimes/gziphandler version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.