Vulnerability Database · Go · Package report

github.com/cespare/xxhash: vulnerability history, versions and safety

github.com/cespare/xxhash 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/cespare/xxhash v1.1.0 i

Updated on 23 Oct 2026

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

Package health score 60/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release v1.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,147 i
  • OpenSSF scorecard 2/10 i
  • Last release 97 months ago i
  • Licence MIT 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/cespare/xxhash, 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-20190104011926-30d0e5bcb75d 04 Jan 2019 none MIT — Details →
v1.1.1-0.20190104011926-30d0e5bcb75d 04 Jan 2019 none MIT — Details →
v1.1.1-0.20190104011727-7052e46dac06 04 Jan 2019 none MIT — Details →
v1.1.1-0.20190104011603-733af8e8a8dd 04 Jan 2019 none MIT — Details →
v1.1.1-0.20190104011350-b821ea84e368 04 Jan 2019 none MIT — Details →
v1.1.1-0.20190101225540-fd51581916f5 01 Jan 2019 none MIT — Details →
v1.1.1-0.20190101220424-26315204797e 01 Jan 2019 none MIT — Details →
v1.1.1-0.20190101220424-bf43f18fa4a9 01 Jan 2019 none MIT — Details →
v0.0.0-20190101194705-9db2993fa675 01 Jan 2019 none MIT — Details →
v0.0.0-20190101194705-f728abcf1928 01 Jan 2019 none MIT — Details →
v1.1.1-0.20190101194705-15c3e70b56a3 01 Jan 2019 none MIT — Details →
v1.1.1-0.20190101194705-9db2993fa675 01 Jan 2019 none MIT — Details →
v1.1.1-0.20190101194705-f728abcf1928 01 Jan 2019 none MIT — Details →
v0.0.0-20181231221321-6e6013902ce9 31 Dec 2018 none MIT — Details →
v1.1.1-0.20181231221321-6e6013902ce9 31 Dec 2018 none MIT — Details →
v1.1.1-0.20181129033603-3c6690985f68 29 Nov 2018 none MIT — Details →
v0.0.0-20181129024025-9573aff1c3fa 29 Nov 2018 none MIT — Details →
v1.1.1-0.20181129024025-9573aff1c3fa 29 Nov 2018 none MIT — Details →
v1.1.1-0.20181129023627-f177858c62a2 29 Nov 2018 none MIT — Details →
v0.0.0-20181017004759-096ff4a8a059 17 Oct 2018 none MIT — Details →
v1.1.1-0.20181017004759-096ff4a8a059 17 Oct 2018 none MIT — Details →
v0.0.0-20180910064531-569f7c8abf1f 10 Sep 2018 none MIT — Details →
v1.1.0 10 Sep 2018 none MIT — Details →
v0.0.0-20180129230333-48099fad606e 29 Jan 2018 none MIT — Details →
v1.0.1-0.20180129230333-48099fad606e 29 Jan 2018 none MIT — Details →
v0.0.0-20171228174439-e4e2bd419cbe 28 Dec 2017 none MIT — Details →
v1.0.1-0.20171228174439-e4e2bd419cbe 28 Dec 2017 none MIT — Details →
v1.0.1-0.20171228172317-9b8290949883 28 Dec 2017 none MIT — Details →
v0.0.0-20170808052227-5c37fe373534 08 Aug 2017 none MIT — Details →
v1.0.0 08 Aug 2017 none MIT — Details →
v0.0.0-20170604094020-1b6d2e40c16b 04 Jun 2017 none MIT — Details →
v0.0.0-20170406043738-b0b3ac4c8896 06 Apr 2017 none MIT — Details →
v0.0.0-20170330212715-09e1e23aaa83 30 Mar 2017 none MIT — Details →
v0.0.0-20170323232612-0c3aa314b221 23 Mar 2017 none MIT — Details →
v0.0.0-20170202221556-7d97cb148919 02 Feb 2017 none MIT — Details →
v0.0.0-20161118035902-4a94f899c20b 18 Nov 2016 none MIT — Details →
v0.0.0-20161118010700-0845171153ba 18 Nov 2016 none MIT — Details →
v0.0.0-20160914073543-1ce10610a70c 14 Sep 2016 none MIT — Details →
v0.0.0-20160831215540-4fbe9820cf29 31 Aug 2016 none MIT — Details →
v0.0.0-20160828094321-17e1db989f60 28 Aug 2016 none MIT — Details →
v0.0.0-20160828015350-285cb94bc62e 28 Aug 2016 none MIT — Details →
v0.0.0-20160827225115-141c235cf4dd 27 Aug 2016 none MIT — Details →
v0.0.0-20160827220742-55f6fd64cfd8 27 Aug 2016 none MIT — Details →

All 43 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/cespare/xxhash

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/cespare/xxhash

Is github.com/cespare/xxhash safe to use?

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

Vulert scores github.com/cespare/xxhash 60/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/cespare/xxhash affected?

No. v1.1.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/cespare/xxhash should I use?

v1.1.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/cespare/xxhash have?

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

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

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