Vulnerability Database · Go · Package report
github.com/jzelinskie/whirlpool: vulnerability history, versions and safety
github.com/jzelinskie/whirlpool 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/jzelinskie/whirlpool v0.0.0-20201016144138-0675e54bb004 i
Updated on 23 Oct 2026
Good news: v0.0.0-20201016144138-0675e54bb004, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.0-20201016144138-0675e54bb004 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20201016144138-0675e54bb004 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20201016144138-0675e54bb004 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 29 i
- OpenSSF scorecard 1/10 i
- Last release 72 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/jzelinskie/whirlpool, 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-20201016144138-0675e54bb004 16 Oct 2020
- v0.0.0-20201015132916-8c7f035bd3b5 15 Oct 2020
- v0.0.0-20170603002051-c19460b8caa6 03 Jun 2017
- v0.0.0-20170602213658-c39e3407821e 02 Jun 2017
- v0.0.0-20121013145138-91685d38df0d 13 Oct 2012
- v0.0.0-20121013124251-abee3ee4316c 13 Oct 2012
- v0.0.0-20120918061455-b120be7c2b85 18 Sep 2012
- v0.0.0-20120907034304-cc1a749cbb11 07 Sep 2012
- v0.0.0-20120822044832-4d5707335271 22 Aug 2012
- v0.0.0-20120512035350-3600b89c1d59 12 May 2012
- v0.0.0-20120510030412-58207fc07ed9 10 May 2012
- v0.0.0-20120417104504-a6770c0190a9 17 Apr 2012
- v0.0.0-20120330045224-03963204ce57 30 Mar 2012
- v0.0.0-20120329055712-3479950b9793 29 Mar 2012
- v0.0.0-20120327222145-288782205dda 27 Mar 2012
- v0.0.0-20120326043158-5796b43ba766 26 Mar 2012
- v0.0.0-20120301010613-6ca25cb49cf0 01 Mar 2012
- v0.0.0-20120223183057-44007067ef81 23 Feb 2012
- v0.0.0-20120220125504-0bd83b9db388 20 Feb 2012
All 19 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/jzelinskie/whirlpool
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/jzelinskie/whirlpool
Is github.com/jzelinskie/whirlpool safe to use?
Vulert has no vulnerabilities on record for github.com/jzelinskie/whirlpool 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/jzelinskie/whirlpool's Vulert package health score?
Vulert scores github.com/jzelinskie/whirlpool 42/100, which reads as risky. 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/jzelinskie/whirlpool affected?
No. v0.0.0-20201016144138-0675e54bb004, 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/jzelinskie/whirlpool should I use?
v0.0.0-20201016144138-0675e54bb004 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/jzelinskie/whirlpool have?
0 vulnerabilities are recorded for github.com/jzelinskie/whirlpool 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/jzelinskie/whirlpool vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/jzelinskie/whirlpool 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/jzelinskie/whirlpool 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/jzelinskie/whirlpool for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jzelinskie/whirlpool version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.