Vulnerability Database · Go · Package report
github.com/speps/go-hashids: vulnerability history, versions and safety
github.com/speps/go-hashids 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/speps/go-hashids v2.0.0+incompatible i
Updated on 23 Oct 2026
Good news: v2.0.0+incompatible, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v2.0.0+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v2.0.0+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v2.0.0+incompatible — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1,376 i
- OpenSSF scorecard 2/10 i
- Last release 99 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/speps/go-hashids, 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.
- v0.0.0-20200604130558-4f009a43556a 04 Jun 2020
- v1.0.1-0.20200604130558-4f009a43556a 04 Jun 2020
- v0.0.0-20181022185652-6ba254bc2e32 22 Oct 2018
- v1.0.1-0.20181022185652-6ba254bc2e32 22 Oct 2018
- v2.0.1-0.20181022185652-6ba254bc2e32+incompatible 22 Oct 2018
- v0.0.0-20180626152748-ad304c6ede07 26 Jun 2018
- v2.0.0+incompatible 26 Jun 2018
- v0.0.0-20180515110130-d5e694adcaa7 15 May 2018
- v1.0.1-0.20180515110130-d5e694adcaa7 15 May 2018
- v0.0.0-20170705204438-c6ced3330f13 05 Jul 2017
- v1.0.1-0.20170705204438-c6ced3330f13 05 Jul 2017
- v0.0.0-20170509210357-2aa1a76a4e7c 09 May 2017
- v1.0.1-0.20170324094635-6fe72284916a 24 Mar 2017
- v0.0.0-20170122122141-4edc50732619 22 Jan 2017
- v1.0.1-0.20170122122141-4edc50732619 22 Jan 2017
- v1.0.1-0.20170122121847-56851513dbdb 22 Jan 2017
- v1.0.1-0.20170117093405-34e8d0b709ec 17 Jan 2017
- v1.0.1-0.20170117093031-f144d50559da 17 Jan 2017
- v0.0.0-20160901103453-552780396682 01 Sep 2016
- v1.0.1-0.20160901103453-552780396682 01 Sep 2016
- v0.0.0-20160609213200-6346448de2d3 09 Jun 2016
- v1.0.1-0.20160609213200-6346448de2d3 09 Jun 2016
- v1.0.1-0.20160609161842-158d28a6ce8f 09 Jun 2016
- v1.0.0 20 Feb 2016
- v0.0.0-20150919095102-3bd0a9294bb4 19 Sep 2015
- v0.0.0-20150517095739-aab5b5b2ddd2 17 May 2015
- v0.0.0-20150421065729-489df7ed34ee 21 Apr 2015
- v0.0.0-20141124221647-7cef70747157 24 Nov 2014
- v0.0.0-20140913201351-214464b91711 13 Sep 2014
All 29 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/speps/go-hashids
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/speps/go-hashids
Is github.com/speps/go-hashids safe to use?
Vulert has no vulnerabilities on record for github.com/speps/go-hashids 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/speps/go-hashids's Vulert package health score?
Vulert scores github.com/speps/go-hashids 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/speps/go-hashids affected?
No. v2.0.0+incompatible, 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/speps/go-hashids should I use?
v2.0.0+incompatible 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/speps/go-hashids have?
0 vulnerabilities are recorded for github.com/speps/go-hashids 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/speps/go-hashids vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/speps/go-hashids 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/speps/go-hashids 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/speps/go-hashids for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/speps/go-hashids version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.