VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/golang/snappy: vulnerability history, versions and safety

github.com/golang/snappy 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/golang/snappy vulnerabilities

Vulert verdict on github.com/golang/snappy v1.0.0 i

Updated on 23 Oct 2026

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

Package health score 63/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release v1.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,574 i
  • OpenSSF scorecard 2/10 i
  • Last release 33 months ago i
  • Licence BSD-3-Clause 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/golang/snappy, 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-20260716114414-9ae09f520e93 16 Jul 2026 none BSD-3-Clause — Details →
v1.0.1-0.20260716114414-9ae09f520e93 16 Jul 2026 none BSD-3-Clause — Details →
v0.0.0-20231225225746-43d5d4cd4e0e 25 Dec 2023 none BSD-3-Clause — Details →
v0.0.4-0.20231225225746-43d5d4cd4e0e 25 Dec 2023 none BSD-3-Clause — Details →
v0.0.5-0.20231225225746-43d5d4cd4e0e 25 Dec 2023 none BSD-3-Clause — Details →
v1.0.0 25 Dec 2023 none BSD-3-Clause — Details →
v0.0.5-0.20221117122232-470b9ed42b44 17 Nov 2022 none BSD-3-Clause — Details →
v0.0.0-20220116011046-fa5810519dcb 16 Jan 2022 none BSD-3-Clause — Details →
v0.0.3-0.20220116011046-fa5810519dcb 16 Jan 2022 none BSD-3-Clause — Details →
v0.0.4-0.20220116011046-fa5810519dcb 16 Jan 2022 none BSD-3-Clause — Details →
v0.0.5-0.20220116011046-fa5810519dcb 16 Jan 2022 none BSD-3-Clause — Details →
v0.0.0-20210608040537-544b4180ac70 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.4 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.4-0.20210608040537-544b4180ac70 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.0-20210608040221-0eaccd476342 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.4-0.20210608040221-0eaccd476342 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.0-20210608035606-3ff355f7bbcd 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.4-0.20210608035606-3ff355f7bbcd 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.0-20210608034659-b9440b43e5e8 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.4-0.20210608034659-b9440b43e5e8 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.0-20210608034643-ef348818abe4 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.4-0.20210608034643-ef348818abe4 08 Jun 2021 none BSD-3-Clause — Details →
v0.0.0-20210502035320-33fc3d5d8d99 02 May 2021 none BSD-3-Clause — Details →
v0.0.4-0.20210502035320-33fc3d5d8d99 02 May 2021 none BSD-3-Clause — Details →
v0.0.4-0.20210420171625-b46926bc8ad2 20 Apr 2021 none BSD-3-Clause — Details →
v0.0.4-0.20210412063441-e149cdd03f0f 12 Apr 2021 none BSD-3-Clause — Details →
v0.0.0-20201103224600-674baa8c7fc3 03 Nov 2020 none BSD-3-Clause — Details →
v0.0.3 03 Nov 2020 none BSD-3-Clause — Details →
v0.0.3-0.20201103224600-674baa8c7fc3 03 Nov 2020 none BSD-3-Clause — Details →
v0.0.3-0.20201002154934-f81760ec4c92 02 Oct 2020 none BSD-3-Clause — Details →
v0.0.0-20200707131729-196ae77b8a26 07 Jul 2020 none BSD-3-Clause — Details →
v0.0.2 07 Jul 2020 none BSD-3-Clause — Details →
v0.0.2-0.20200707131729-196ae77b8a26 07 Jul 2020 none BSD-3-Clause — Details →
v0.0.2-0.20200707131105-1801c13ca212 07 Jul 2020 none BSD-3-Clause — Details →
v0.0.2-0.20200701030152-ea060ccb7223 01 Jul 2020 none BSD-3-Clause — Details →
v0.0.2-0.20200217183943-0a27eb7fa2ce 17 Feb 2020 none BSD-3-Clause — Details →
v0.0.0-20190904063534-ff6b7dc882cf 04 Sep 2019 none BSD-3-Clause — Details →
v0.0.2-0.20190904063534-ff6b7dc882cf 04 Sep 2019 none BSD-3-Clause — Details →
v0.0.2-0.20190904062947-059a9b19228c 04 Sep 2019 none BSD-3-Clause — Details →
v0.0.2-0.20190904062717-c9879f99e6b4 04 Sep 2019 none BSD-3-Clause — Details →
v0.0.2-0.20190904062623-5610373d2fa9 04 Sep 2019 none BSD-3-Clause — Details →
v0.0.2-0.20190901175524-f6ad6c8bb828 01 Sep 2019 none BSD-3-Clause — Details →
v0.0.2-0.20190901175302-efb0d863a3fb 01 Sep 2019 none BSD-3-Clause — Details →
v0.0.0-20190218232222-2a8bb927dd31 18 Feb 2019 none BSD-3-Clause — Details →
v0.0.1 18 Feb 2019 none BSD-3-Clause — Details →
v0.0.2-0.20190218232222-2a8bb927dd31 18 Feb 2019 none BSD-3-Clause — Details →
v0.0.0-20190211213528-f05e7a5086fe 11 Feb 2019 none BSD-3-Clause — Details →
v0.0.0-20180518054509-2e65f85255db 18 May 2018 none BSD-3-Clause — Details →
v0.0.0-20180518051859-e45cd318e0c1 18 May 2018 none BSD-3-Clause — Details →
v0.0.0-20170901113827-da2bb3382a39 01 Sep 2017 none BSD-3-Clause — Details →
v0.0.0-20170328120551-35a8406c2110 28 Mar 2017 none BSD-3-Clause — Details →
v0.0.0-20170215233205-553a64147049 15 Feb 2017 none BSD-3-Clause — Details →
v0.0.0-20170125070754-0d9c4c05f138 25 Jan 2017 none BSD-3-Clause — Details →
v0.0.0-20170119014723-7db9049039a0 19 Jan 2017 none BSD-3-Clause — Details →
v0.0.0-20170118105153-5a0054d7b7e6 18 Jan 2017 none BSD-3-Clause — Details →
v0.0.0-20160529050041-d9eb7a3d35ec 29 May 2016 none BSD-3-Clause — Details →
v0.0.0-20160519033420-d6668316e435 19 May 2016 none BSD-3-Clause — Details →
v0.0.0-20160504221712-d7b1e156f50d 04 May 2016 none BSD-3-Clause — Details →
v0.0.0-20160504214801-aefa7ba4ef30 04 May 2016 none BSD-3-Clause — Details →
v0.0.0-20160429230219-43fea289edce 29 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160429052803-b62d312cd2a7 29 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160429010633-2b2933512044 29 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160424003234-ec642410cd03 24 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160424000712-7dddae14f78f 24 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160423021741-0c43e98dfe3f 23 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160416051534-774a97396f7b 16 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160414084710-3588d1dd8495 14 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160412003728-fa0b0e6289e9 12 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160411020628-ef80b33e8738 11 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160410062943-70f093abd7c1 10 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160407051505-cef980a12b31 07 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160407050902-6218a584d0b0 07 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160404000540-857ad66e003f 04 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160403124017-0e8b256be277 03 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160403011801-8939696c2214 03 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160402052240-d1f56d222213 02 Apr 2016 none BSD-3-Clause — Details →
v0.0.0-20160304054822-5f1c01d9f64b 04 Mar 2016 none BSD-3-Clause — Details →
v0.0.0-20160226063025-427fb6fc0799 26 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160226040801-03ee571cd354 26 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160225125504-12528fe03377 25 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160223124910-a64ab7d6ec90 23 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160223021251-939eddc12b3b 23 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160222024450-e2923611954f 22 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160222014436-bf2ded9d81f5 22 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160214055435-d1d908a252c2 14 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160213000601-51195a16b052 13 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160212113041-5979233c5d62 12 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160212054907-07070fd417b5 12 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160211061040-799c780093d6 11 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160211044451-0fd139378be7 11 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160210064713-75a5f0a18524 10 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160210033144-4e2aa98ebb3b 10 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160208223310-a3e588b9ea76 08 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160207054855-894fd4616c89 07 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160207052646-7269ba46dc70 07 Feb 2016 none BSD-3-Clause — Details →
v0.0.0-20160129023148-1963d058044b 29 Jan 2016 none BSD-3-Clause — Details →
v0.0.0-20160129023043-45146e5b8d6d 29 Jan 2016 none BSD-3-Clause — Details →
v0.0.0-20151222230431-405fe506d8fb 22 Dec 2015 none BSD-3-Clause — Details →
v0.0.0-20150730031844-723cc1e459b8 30 Jul 2015 none BSD-3-Clause — Details →
v0.0.0-20150722033058-0c7f8a7704bf 22 Jul 2015 none BSD-3-Clause — Details →
v0.0.0-20150721071430-ec7b9243422b 21 Jul 2015 none — — Details →
v0.0.0-20150721070725-28028bb0f19d 21 Jul 2015 none — — Details →
v0.0.0-20150717073015-f4b10fa94214 17 Jul 2015 none — — Details →
v0.0.0-20150717072107-2a6d64140dee 17 Jul 2015 none — — Details →
v0.0.0-20150717071016-6bb800503734 17 Jul 2015 none — — Details →
v0.0.0-20150611082312-3399c788ea99 11 Jun 2015 none — — Details →
v0.0.0-20150611081830-c5eccb269afa 11 Jun 2015 none — — Details →
v0.0.0-20150608215352-eaa750b9bf4d 08 Jun 2015 none — — Details →
v0.0.0-20150514054436-a911026e1ffa 14 May 2015 none — — Details →
v0.0.0-20150210042334-156a073208e1 10 Feb 2015 none — — Details →
v0.0.0-20150210005634-4c0868570206 10 Feb 2015 none — — Details →
v0.0.0-20150209042042-5c1be99682ee 09 Feb 2015 none — — Details →
v0.0.0-20130220111603-ce8acff4829e 20 Feb 2013 none — — Details →
v0.0.0-20130220003125-b86a88ac1861 20 Feb 2013 none — — Details →
v0.0.0-20130220002928-381d3abc0cb0 20 Feb 2013 none — — Details →
v0.0.0-20130212033832-781077d9bfb5 12 Feb 2013 none — — Details →
v0.0.0-20120606094212-2d44ef2b92cc 06 Jun 2012 none — — Details →
v0.0.0-20120203225527-f23747f90227 03 Feb 2012 none — — Details →
v0.0.0-20111222233738-06ee9ff6bc33 22 Dec 2011 none — — Details →
v0.0.0-20111107233350-5b93c920dbd1 07 Nov 2011 none — — Details →

The newest 120 of 123 versions Vulert tracks. 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/golang/snappy

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/golang/snappy

Is github.com/golang/snappy safe to use?

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

Vulert scores github.com/golang/snappy 63/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/golang/snappy affected?

No. v1.0.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/golang/snappy should I use?

v1.0.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/golang/snappy have?

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

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

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