Vulnerability Database · Go · Package report
github.com/ipfs/go-ipfs-delay: vulnerability history, versions and safety
github.com/ipfs/go-ipfs-delay 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-ipfs-delay v0.0.1 i
Updated on 23 Oct 2026
Good news: v0.0.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 6 i
- OpenSSF scorecard 3/10 i
- Last release 91 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/ipfs/go-ipfs-delay, 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.2-0.20260222154756-0d22e5ff21b4 22 Feb 2026
- v0.0.2-0.20250821073257-23c4e2a0046d 21 Aug 2025
- v0.0.2-0.20250328130844-a6a88e57ea42 28 Mar 2025
- v0.0.2-0.20250216200250-eea834bdecfc 16 Feb 2025
- v0.0.2-0.20240826102727-ac78a88a3b14 26 Aug 2024
- v0.0.2-0.20240322071834-78549bb2a46d 22 Mar 2024
- v0.0.2-0.20240314112707-cbca99efc825 14 Mar 2024
- v0.0.2-0.20240131173700-f9e276694875 31 Jan 2024
- v0.0.2-0.20230814133713-c3e48a271dff 14 Aug 2023
- v0.0.2-0.20230814062147-2dd0e17fb662 14 Aug 2023
- v0.0.2-0.20230813164101-b870ee913c7e 13 Aug 2023
- v0.0.2-0.20230628085013-72f833d334c6 28 Jun 2023
- v0.0.2-0.20230614111425-ea6848a6abc5 14 Jun 2023
- v0.0.2-0.20230208150113-22951c93da55 08 Feb 2023
- v0.0.2-0.20220823165221-eabb63fbbb03 23 Aug 2022
- v0.0.2-0.20211210141645-789ac6f6c047 10 Dec 2021
- v0.0.2-0.20210817145523-6fd6c59b92cc 17 Aug 2021
- v0.0.2-0.20210601173823-7587d1f10600 01 Jun 2021
- v0.0.2-0.20210513162426-aaf814712c2d 13 May 2021
- v0.0.2-0.20200504101203-131d5ffc85a8 04 May 2020
- v0.0.1 28 Feb 2019
- v0.0.0-20181109222059-70721b86a9a8 09 Nov 2018
- v0.0.0-20180209124744-d0bfb5937b92 09 Feb 2018
- v0.0.0-20160619125909-203052258b59 19 Jun 2016
All 24 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-ipfs-delay
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-ipfs-delay
Is github.com/ipfs/go-ipfs-delay safe to use?
Vulert has no vulnerabilities on record for github.com/ipfs/go-ipfs-delay 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-ipfs-delay's Vulert package health score?
Vulert scores github.com/ipfs/go-ipfs-delay 45/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/ipfs/go-ipfs-delay affected?
No. v0.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/ipfs/go-ipfs-delay should I use?
v0.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/ipfs/go-ipfs-delay have?
0 vulnerabilities are recorded for github.com/ipfs/go-ipfs-delay 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-ipfs-delay vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/ipfs/go-ipfs-delay 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-ipfs-delay 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-ipfs-delay for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/ipfs/go-ipfs-delay version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.