VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/minio/highwayhash: vulnerability history, versions and safety

github.com/minio/highwayhash 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/minio/highwayhash vulnerabilities

Vulert verdict on github.com/minio/highwayhash v1.0.4 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release v1.0.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 958 i
  • OpenSSF scorecard 3/10 i
  • Last release 11 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/minio/highwayhash, 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-20251030100505-070ab1a87a76 30 Oct 2025 none Apache-2.0 — Details →
v1.0.4 30 Oct 2025 none Apache-2.0 — Details →
v1.0.4-0.20251030100505-070ab1a87a76 30 Oct 2025 none Apache-2.0 — Details →
v0.0.0-20241227125823-62e677f3384e 27 Dec 2024 none Apache-2.0 — Details →
v1.0.4-0.20241227125823-62e677f3384e 27 Dec 2024 none Apache-2.0 — Details →
v1.0.4-0.20241227075839-d7d7e9bcd9d7 27 Dec 2024 none Apache-2.0 — Details →
v1.0.3 26 Jun 2024 none Apache-2.0 — Details →
v1.0.3-0.20240626074931-030a8b332625 26 Jun 2024 none Apache-2.0 — Details →
v1.0.3-0.20240626074931-3346a584da73 26 Jun 2024 none Apache-2.0 — Details →
v1.0.3-0.20240501210222-6a9c19b1156f 01 May 2024 none Apache-2.0 — Details →
v1.0.3-0.20230516131822-1304c103e59f 16 May 2023 none Apache-2.0 — Details →
v1.0.3-0.20230225023203-1a96f281b5c6 25 Feb 2023 none Apache-2.0 — Details →
v1.0.3-0.20230104182448-0f93442fe71f 04 Jan 2023 none Apache-2.0 — Details →
v1.0.3-0.20230104182448-64d40fd836ef 04 Jan 2023 none Apache-2.0 — Details →
v1.0.3-0.20230104182448-9cb37b8cb4e3 04 Jan 2023 none Apache-2.0 — Details →
v1.0.3-0.20230104182448-c09d704b3a73 04 Jan 2023 none Apache-2.0 — Details →
v1.0.3-0.20221018233349-e85f5d513ec0 18 Oct 2022 none Apache-2.0 — Details →
v1.0.2 25 Mar 2021 none Apache-2.0 — Details →
v1.0.1 16 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20200522172658-f1ce81142634 22 May 2020 none Apache-2.0 — Details →
v1.0.1-0.20200522172658-f1ce81142634 22 May 2020 none Apache-2.0 — Details →
v1.0.1-0.20200522172153-be7fb2e09d9a 22 May 2020 none Apache-2.0 — Details →
v1.0.1-0.20200516015009-0bb43c8ea73a 16 May 2020 none MIT — Details →
v1.0.1-0.20200514202246-10917f65e974 14 May 2020 none MIT — Details →
v0.0.0-20190131021015-02ca4b43caa3 31 Jan 2019 none MIT — Details →
v1.0.0 31 Jan 2019 none MIT — Details →
v0.0.0-20190112144901-fc990dfafa15 12 Jan 2019 none MIT — Details →
v0.0.0-20181220011308-93ed73d64169 20 Dec 2018 none MIT — Details →
v0.0.0-20180501080913-85fc8a2dacad 01 May 2018 none MIT — Details →
v0.0.0-20180308212404-9c7e959d92fc 08 Mar 2018 none MIT — Details →
v0.0.0-20180109224026-1ea1b5fce73b 09 Jan 2018 none MIT — Details →
v0.0.0-20180108205340-f178208335fe 08 Jan 2018 none MIT — Details →
v0.0.0-20180103223822-fd0b0262e003 03 Jan 2018 none MIT — Details →
v0.0.0-20170810203041-017df6b4983c 10 Aug 2017 none MIT — Details →
v0.0.0-20170809015821-7bd6599cb37d 09 Aug 2017 none MIT — Details →
v0.0.0-20170803191906-1970fe2b8303 03 Aug 2017 none MIT — Details →
v0.0.0-20170803023055-1e34b0eb5fee 03 Aug 2017 none MIT — Details →
v0.0.0-20170802005801-a6b9dae543bd 02 Aug 2017 none MIT — Details →
v0.0.0-20170801020658-1899d1d69e7d 01 Aug 2017 none MIT — Details →
v0.0.0-20170801001228-9d5888a49264 01 Aug 2017 none MIT — Details →

All 40 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/minio/highwayhash

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/minio/highwayhash

Is github.com/minio/highwayhash safe to use?

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

Vulert scores github.com/minio/highwayhash 75/100, which reads as in good shape. 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/minio/highwayhash affected?

No. v1.0.4, 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/minio/highwayhash should I use?

v1.0.4 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/minio/highwayhash have?

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

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

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