Vulnerability Database · Go · Package report
github.com/ipfs/go-verifcid: vulnerability history, versions and safety
github.com/ipfs/go-verifcid 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/ipfs/go-verifcid v0.0.3 i
Updated on 23 Oct 2026
Good news: v0.0.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 3 i
- OpenSSF scorecard 3/10 i
- Last release 40 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/ipfs/go-verifcid, 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.4-0.20230614111344-4c21a4766b8c 14 Jun 2023
- v0.0.3 25 May 2023
- v0.0.3-0.20230222232948-05a51ce8b9e8 22 Feb 2023
- v0.0.3-0.20230222232912-062f61997482 22 Feb 2023
- v0.0.3-0.20230208150400-c45e93b5f91e 08 Feb 2023
- v0.0.3-0.20220823165148-d870bba8ca7e 23 Aug 2022
- v0.0.2 12 Aug 2022
- v0.0.0-20220721095420-a633a921b660 21 Jul 2022
- v0.0.2-0.20220721095420-a633a921b660 21 Jul 2022
- v0.0.2-0.20220627104718-9c75188417e7 27 Jun 2022
- v0.0.2-0.20220613125228-46876f413195 13 Jun 2022
- v0.0.2-0.20220404163023-e2bc3fdc2ec2 04 Apr 2022
- v0.0.2-0.20211210154057-52ec7f147db0 10 Dec 2021
- v0.0.2-0.20210818121805-6dc8fb6b20b1 18 Aug 2021
- v0.0.0-20210601174317-eaca6d2fcfed 01 Jun 2021
- v0.0.2-0.20210601174317-eaca6d2fcfed 01 Jun 2021
- v0.0.2-0.20200504101507-a9d170f0d924 04 May 2020
- v0.0.0-20190310142444-db47d7734963 10 Mar 2019
- v0.0.2-0.20190310142444-db47d7734963 10 Mar 2019
- v0.0.2-0.20190302174447-6d7e15d162b2 02 Mar 2019
- v0.0.1 02 Mar 2019
- v0.0.0-20190221041709-865373a50471 21 Feb 2019
- v0.0.0-20181102235604-8909da14ac6d 02 Nov 2018
- v0.0.0-20180911234452-8662485027c2 11 Sep 2018
- v0.0.0-20180822000959-f9c8f6d8aa7a 22 Aug 2018
- v0.0.0-20180815152755-76135a533a9e 15 Aug 2018
- v0.0.0-20180811010023-6f33d28bf5c6 11 Aug 2018
- v0.0.0-20180728004902-1aa772db799d 28 Jul 2018
All 28 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/ipfs/go-verifcid
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/ipfs/go-verifcid
Is github.com/ipfs/go-verifcid safe to use?
Vulert has no vulnerabilities on record for github.com/ipfs/go-verifcid 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/ipfs/go-verifcid's Vulert package health score?
Vulert scores github.com/ipfs/go-verifcid 52/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/ipfs/go-verifcid affected?
No. v0.0.3, 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/ipfs/go-verifcid should I use?
v0.0.3 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/ipfs/go-verifcid have?
0 vulnerabilities are recorded for github.com/ipfs/go-verifcid 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/ipfs/go-verifcid vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/ipfs/go-verifcid 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/ipfs/go-verifcid 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/ipfs/go-verifcid for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/ipfs/go-verifcid version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.