Vulnerability Database · Go · Package report

github.com/minio/sha256-simd: vulnerability history, versions and safety

github.com/minio/sha256-simd 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/minio/sha256-simd v1.0.1 i

Updated on 23 Oct 2026

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

Package health score 63/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release v1.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,039 i
  • OpenSSF scorecard 2/10 i
  • Last release 44 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/sha256-simd, 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-20230222114820-6096f891a77b 22 Feb 2023 none Apache-2.0 — Details →
v1.0.1 22 Feb 2023 none Apache-2.0 — Details →
v1.0.1-0.20230222114820-6096f891a77b 22 Feb 2023 none Apache-2.0 — Details →
v1.0.1-0.20230130105256-d9c3aea9e949 30 Jan 2023 none Apache-2.0 — Details →
v1.0.1-0.20221018232555-9057a89806a9 18 Oct 2022 none Apache-2.0 — Details →
v0.0.0-20210617151322-99e45fae3395 17 Jun 2021 none Apache-2.0 — Details →
v1.0.1-0.20210617151322-99e45fae3395 17 Jun 2021 none Apache-2.0 — Details →
v1.0.1-0.20210406080713-f73b335d2795 06 Apr 2021 none Apache-2.0 — Details →
v0.1.2 22 Feb 2021 none Apache-2.0 — Details →
v0.1.2-0.20210222172656-6a57409d8e0f 22 Feb 2021 none Apache-2.0 — Details →
v1.0.0 22 Feb 2021 none Apache-2.0 — Details →
v0.0.0-20190917233721-f675151bb5e1 17 Sep 2019 none Apache-2.0 — Details →
v0.1.2-0.20190917233721-f675151bb5e1 17 Sep 2019 none Apache-2.0 — Details →
v0.0.0-20190913151208-6de447530771 13 Sep 2019 none Apache-2.0 — Details →
v0.1.1 13 Sep 2019 none Apache-2.0 — Details →
v0.1.1-0.20190913151208-6de447530771 13 Sep 2019 none Apache-2.0 — Details →
v0.1.1-0.20190906165320-649be62517ba 06 Sep 2019 none Apache-2.0 — Details →
v0.1.1-0.20190905233038-e57049a46bfc 05 Sep 2019 none Apache-2.0 — Details →
v0.0.0-20190328051042-05b4dd3047e5 28 Mar 2019 none Apache-2.0 — Details →
v0.1.0 28 Mar 2019 none Apache-2.0 — Details →
v0.0.0-20190319235355-3557f3d43a12 19 Mar 2019 none Apache-2.0 — Details →
v0.0.0-20190317211740-0d7ea3c244ee 17 Mar 2019 none Apache-2.0 — Details →
v0.0.0-20190131020904-2d45a736cd16 31 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190117184323-cc1980cb0338 17 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190108234304-79eac576c45d 08 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190105025725-66352e71c5e1 05 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20190104231041-e529fa194128 04 Jan 2019 none Apache-2.0 — Details →
v0.0.0-20181005183134-51976451ce19 05 Oct 2018 none Apache-2.0 — Details →
v0.0.0-20181005182913-047d69f798f9 05 Oct 2018 none Apache-2.0 — Details →
v0.0.0-20171213220625-ad98a36ba0da 13 Dec 2017 none Apache-2.0 — Details →
v0.0.0-20171211213237-e8f1b272f834 11 Dec 2017 none Apache-2.0 — Details →
v0.0.0-20171209190641-96c8f86cdb67 09 Dec 2017 none Apache-2.0 — Details →
v0.0.0-20171208221113-6898e4f79f46 08 Dec 2017 none Apache-2.0 — Details →
v0.0.0-20171119044428-1e906017f630 19 Nov 2017 none Apache-2.0 — Details →
v0.0.0-20171107223716-c985c18ac142 07 Nov 2017 none Apache-2.0 — Details →
v0.0.0-20170828173933-43ed500fe4d4 28 Aug 2017 none Apache-2.0 — Details →
v0.0.0-20170424153414-f3ec2e4d36d4 24 Apr 2017 none Apache-2.0 — Details →
v0.0.0-20170404222936-6124d070eb4e 04 Apr 2017 none Apache-2.0 — Details →
v0.0.0-20170304192251-187c585ea0bb 04 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20170304064530-1ba440bb00bb 04 Mar 2017 none Apache-2.0 — Details →
v0.0.0-20161219231730-e82e73b77576 19 Dec 2016 none Apache-2.0 — Details →
v0.0.0-20161015215236-343f5933f71f 15 Oct 2016 none Apache-2.0 — Details →
v0.0.0-20160907002930-672e7bc9f348 07 Sep 2016 none Apache-2.0 — Details →
v0.0.0-20160816222511-6f50cd1d784b 16 Aug 2016 none Apache-2.0 — Details →
v0.0.0-20160816192147-62bacb8d2c5d 16 Aug 2016 none Apache-2.0 — Details →
v0.0.0-20160728211057-8058cafa697e 28 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160727155639-15470d9766f9 27 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160727002704-0d2baa051e68 27 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160726055358-0eda84c0199c 26 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160724200131-cc9dfe912511 24 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160723220307-0859071b6180 23 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160723003848-036411cd4ad2 23 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160723003830-c425af2f4191 23 Jul 2016 none Apache-2.0 — Details →
v0.0.0-20160722232117-82721d81cf25 22 Jul 2016 none Apache-2.0 — Details →

All 54 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/sha256-simd

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/sha256-simd

Is github.com/minio/sha256-simd safe to use?

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

Vulert scores github.com/minio/sha256-simd 63/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/minio/sha256-simd affected?

No. v1.0.1, 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/sha256-simd should I use?

v1.0.1 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/sha256-simd have?

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

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

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