Vulnerability Database · Go · Package report

github.com/filecoin-project/go-fil-commp-hashhash: vulnerability history, versions and safety

github.com/filecoin-project/go-fil-commp-hashhash 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/filecoin-project/go-fil-commp-hashhash v0.4.0 i

Updated on 23 Oct 2026

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

Package health score 61/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.4.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 10 i
  • OpenSSF scorecard 2/10 i
  • Last release 6 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/filecoin-project/go-fil-commp-hashhash, 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-20261002033258-9883aba28804 02 Oct 2026 none Apache-2.0 — Details →
v0.4.1-0.20261002033258-9883aba28804 02 Oct 2026 none Apache-2.0 — Details →
v0.0.0-20260801081431-256368516783 01 Aug 2026 none Apache-2.0 — Details →
v0.4.1-0.20260801081431-256368516783 01 Aug 2026 none Apache-2.0 — Details →
v0.0.0-20260420025110-283138b0d1ef 20 Apr 2026 none Apache-2.0 — Details →
v0.4.0 20 Apr 2026 none Apache-2.0 — Details →
v0.0.0-20260222154827-c12522866bed 22 Feb 2026 none Apache-2.0 — Details →
v0.3.1-0.20260222154827-c12522866bed 22 Feb 2026 none Apache-2.0 — Details →
v0.0.0-20260127052742-95ca9ec7b18c 27 Jan 2026 none Apache-2.0 — Details →
v0.3.0 27 Jan 2026 none Apache-2.0 — Details →
v0.2.1-0.20260107152413-d6952fff4f39 07 Jan 2026 none Apache-2.0 — Details →
v0.0.0-20250821073326-fe57ba85ecfc 21 Aug 2025 none Apache-2.0 — Details →
v0.2.1-0.20250821073326-fe57ba85ecfc 21 Aug 2025 none Apache-2.0 — Details →
v0.2.1-0.20250216200316-4dd194bf1660 16 Feb 2025 none Apache-2.0 — Details →
v0.0.0-20240826011246-cf1f8fb159c8 26 Aug 2024 none Apache-2.0 — Details →
v0.2.1-0.20240826011246-cf1f8fb159c8 26 Aug 2024 none Apache-2.0 — Details →
v0.0.0-20240322071901-04f16959cec8 22 Mar 2024 none Apache-2.0 — Details →
v0.2.1-0.20240322071901-04f16959cec8 22 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240314112730-b13e5df63222 14 Mar 2024 none Apache-2.0 — Details →
v0.2.1-0.20240314112730-b13e5df63222 14 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20230814133737-d69bc9eb6296 14 Aug 2023 none Apache-2.0 — Details →
v0.2.1-0.20230814133737-d69bc9eb6296 14 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230811065821-2e9c683db589 11 Aug 2023 none Apache-2.0 — Details →
v0.2.1-0.20230811065821-2e9c683db589 11 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230807110556-86d57f8d8427 07 Aug 2023 none Apache-2.0 — Details →
v0.2.1-0.20230807110556-86d57f8d8427 07 Aug 2023 none Apache-2.0 — Details →
v0.2.1-0.20230307094507-e82ff3758f4c 07 Mar 2023 none Apache-2.0 — Details →
v0.2.1-0.20230306222607-8f8a4fc56ab1 06 Mar 2023 none Apache-2.0 — Details →
v0.2.0 06 Mar 2023 none Apache-2.0 — Details →
v0.1.1-0.20230222124358-bb185064c764 22 Feb 2023 none Apache-2.0 — Details →
v0.0.0-20230209104829-259b647a49b0 09 Feb 2023 none Apache-2.0 — Details →
v0.1.1-0.20230209104829-259b647a49b0 09 Feb 2023 none Apache-2.0 — Details →
v0.0.0-20211116202452-3c2488d36979 16 Nov 2021 none Apache-2.0 — Details →
v0.1.1-0.20211116202452-3c2488d36979 16 Nov 2021 none Apache-2.0 — Details →
v0.1.1-0.20211008224528-fe93a7ff60dc 08 Oct 2021 none Apache-2.0 — Details →
v0.0.0-20210716094257-d9e25dd4bb3d 16 Jul 2021 none Apache-2.0 — Details →
v0.1.1-0.20210716094257-d9e25dd4bb3d 16 Jul 2021 none Apache-2.0 — Details →
v0.1.1-0.20210421113354-0bfad422d2c3 21 Apr 2021 none Apache-2.0 — Details →
v0.1.1-0.20210420220456-4fd405a0def9 20 Apr 2021 none Apache-2.0 — Details →
v0.1.1-0.20210419202552-55d6648a632e 19 Apr 2021 none Apache-2.0 — Details →
v0.1.1-0.20210408023918-78db6aee9f94 08 Apr 2021 none Apache-2.0 — Details →
v0.1.1-0.20210329205621-d04a72c322d0 29 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210329194435-942e747c33ad 29 Mar 2021 none Apache-2.0 — Details →
v0.1.0 29 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210329070555-d36b89a2504c 29 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210326183129-9552167b49b4 26 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210326165859-eddc89b232cb 26 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210324114335-05a6c7b12b66 24 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210322200634-d31e97c09c7a 22 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210322190520-b873fe623f79 22 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210322171349-4274b69e90e1 22 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210322170637-a4b97383a10d 22 Mar 2021 none Apache-2.0 — Details →

All 52 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/filecoin-project/go-fil-commp-hashhash

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/filecoin-project/go-fil-commp-hashhash

Is github.com/filecoin-project/go-fil-commp-hashhash safe to use?

Vulert has no vulnerabilities on record for github.com/filecoin-project/go-fil-commp-hashhash 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/filecoin-project/go-fil-commp-hashhash's Vulert package health score?

Vulert scores github.com/filecoin-project/go-fil-commp-hashhash 61/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/filecoin-project/go-fil-commp-hashhash affected?

No. v0.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/filecoin-project/go-fil-commp-hashhash should I use?

v0.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/filecoin-project/go-fil-commp-hashhash have?

0 vulnerabilities are recorded for github.com/filecoin-project/go-fil-commp-hashhash 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/filecoin-project/go-fil-commp-hashhash vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/filecoin-project/go-fil-commp-hashhash 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/filecoin-project/go-fil-commp-hashhash 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/filecoin-project/go-fil-commp-hashhash for upcoming vulnerabilities?

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