VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/klauspost/readahead: vulnerability history, versions and safety

github.com/klauspost/readahead 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/klauspost/readahead vulnerabilities

Vulert verdict on github.com/klauspost/readahead v1.4.0 i

Updated on 23 Oct 2026

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

Package health score 49/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.4.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 244 i
  • OpenSSF scorecard 2/10 i
  • Last release 57 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/klauspost/readahead, 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
v1.4.1-0.20240815115533-cc3ed315bd39 15 Aug 2024 none MIT — Details →
v1.4.1-0.20220829151949-9354345239e0 29 Aug 2022 none MIT — Details →
v1.3.2-0.20220111113938-139798c3e21d 11 Jan 2022 none MIT — Details →
v1.4.0 11 Jan 2022 none MIT — Details →
v1.3.2-0.20220111102706-2c89e53e4d8d 11 Jan 2022 none MIT — Details →
v1.3.2-0.20220111095427-6fcab83fa739 11 Jan 2022 none MIT — Details →
v1.3.2-0.20220111085714-b07e21de1fd3 11 Jan 2022 none MIT — Details →
v1.3.1 05 Nov 2019 none MIT — Details →
v0.0.0-20190217110753-0d07bc3753e3 17 Feb 2019 none MIT — Details →
v1.3.0 17 Feb 2019 none MIT — Details →
v0.0.0-20171007124306-7f90b27d8111 07 Oct 2017 none MIT — Details →
v1.2.0 07 Oct 2017 none MIT — Details →
v1.2.1-0.20171007124306-7f90b27d8111 07 Oct 2017 none MIT — Details →
v0.0.0-20170716114535-d2a445e8b76d 16 Jul 2017 none MIT — Details →
v0.0.0-20160219142305-e2cfa52e5c85 19 Feb 2016 none MIT — Details →

All 15 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/klauspost/readahead

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/klauspost/readahead

Is github.com/klauspost/readahead safe to use?

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

Vulert scores github.com/klauspost/readahead 49/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/klauspost/readahead affected?

No. v1.4.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/klauspost/readahead should I use?

v1.4.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/klauspost/readahead have?

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

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

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