Vulnerability Database · Go · Package report
github.com/drand/drand/v2: vulnerability history, versions and safety
github.com/drand/drand/v2 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/drand/drand/v2 v2.1.8 i
Updated on 23 Oct 2026
Good news: v2.1.8, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Widely used
- Community Moderate
What to do: Stay on v2.1.8 or newer. This can change: a vulnerability disclosed tomorrow can affect v2.1.8 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v2.1.8 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 848 i
- OpenSSF scorecard 5/10 i
- Last release this month 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/drand/drand/v2, 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.
- v2.1.8 07 Oct 2026
- v2.1.7 22 Jul 2026
- v2.1.7-0.20260722165506-2363f3b9ba5f 22 Jul 2026
- v2.1.7-0.20260630175044-9f2386e211c7 30 Jun 2026
- v2.1.7-0.20260616155805-2becdaa17261 16 Jun 2026
- v2.1.6 02 Apr 2026
- v2.1.5 25 Mar 2026
- v2.1.4 15 Dec 2025
- v2.1.4-0.20251029191119-8228476b1d2b 29 Oct 2025
- v2.1.4-0.20250930154724-4a8ab74f0e94 30 Sep 2025
- v2.1.4-pre2 29 Sep 2025
- v2.1.4-pre1 29 Sep 2025
- v2.1.4-0.20250725131636-be545f554820 25 Jul 2025
- v2.1.3 27 Jun 2025
- v2.1.2 25 Apr 2025
- v2.1.1 15 Apr 2025
- v2.1.0 19 Feb 2025
- v2.0.6 14 Feb 2025
- v2.0.5-0.20241218123705-9af935c5638e 18 Dec 2024
- v2.0.5-0.20240927173018-2b007cb3b341 27 Sep 2024
- v2.0.4 25 Sep 2024
- v2.0.3 11 Sep 2024
- v2.0.3-0.20240911125235-30813b010e3a 11 Sep 2024
- v2.0.3-0.20240903205035-ec2eb71df70a 03 Sep 2024
- v2.0.2 16 Jul 2024
- v2.0.0-20240703124230-eaad265011d6 03 Jul 2024
- v2.0.0-20240629135448-09bd8d4d1c12 29 Jun 2024
- v2.0.1 24 Jun 2024
- v2.0.0 19 Jun 2024
- v2.0.6-testnet 10 May 2024
- v2.0.5-testnet.0.20240320202519-60bf17b13675 20 Mar 2024
- v2.0.5-testnet.0.20240306023503-dc4c1de60df5 06 Mar 2024
- v2.0.5-testnet 23 Feb 2024
- v2.0.4-testnet 21 Feb 2024
- v2.0.3-testnet 21 Feb 2024
- v2.0.1-testnet.0.20240220131156-cbc7ea2f3d09 20 Feb 2024
- v2.0.2-testnet 20 Feb 2024
- v2.0.1-testnet 10 Jan 2024
- v2.0.0-testnet 10 Jan 2024
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v2.1.8 | 07 Oct 2026 | none | Apache-2.0 | — | Details → |
| v2.1.7 | 22 Jul 2026 | none | Apache-2.0 | — | Details → |
| v2.1.7-0.20260722165506-2363f3b9ba5f | 22 Jul 2026 | none | Apache-2.0 | — | Details → |
| v2.1.7-0.20260630175044-9f2386e211c7 | 30 Jun 2026 | none | Apache-2.0 | — | Details → |
| v2.1.7-0.20260616155805-2becdaa17261 | 16 Jun 2026 | none | Apache-2.0 | — | Details → |
| v2.1.6 | 02 Apr 2026 | none | Apache-2.0 | — | Details → |
| v2.1.5 | 25 Mar 2026 | none | Apache-2.0 | — | Details → |
| v2.1.4 | 15 Dec 2025 | none | Apache-2.0 | — | Details → |
| v2.1.4-0.20251029191119-8228476b1d2b | 29 Oct 2025 | none | Apache-2.0 | — | Details → |
| v2.1.4-0.20250930154724-4a8ab74f0e94 | 30 Sep 2025 | none | Apache-2.0 | — | Details → |
| v2.1.4-pre2 | 29 Sep 2025 | none | Apache-2.0 | — | Details → |
| v2.1.4-pre1 | 29 Sep 2025 | none | Apache-2.0 | — | Details → |
| v2.1.4-0.20250725131636-be545f554820 | 25 Jul 2025 | none | Apache-2.0 | — | Details → |
| v2.1.3 | 27 Jun 2025 | none | Apache-2.0 | — | Details → |
| v2.1.2 | 25 Apr 2025 | none | Apache-2.0 | — | Details → |
| v2.1.1 | 15 Apr 2025 | none | Apache-2.0 | — | Details → |
| v2.1.0 | 19 Feb 2025 | none | Apache-2.0 | — | Details → |
| v2.0.6 | 14 Feb 2025 | none | Apache-2.0 | — | Details → |
| v2.0.5-0.20241218123705-9af935c5638e | 18 Dec 2024 | none | Apache-2.0 | — | Details → |
| v2.0.5-0.20240927173018-2b007cb3b341 | 27 Sep 2024 | none | Apache-2.0 | — | Details → |
| v2.0.4 | 25 Sep 2024 | none | Apache-2.0 | — | Details → |
| v2.0.3 | 11 Sep 2024 | none | Apache-2.0 | — | Details → |
| v2.0.3-0.20240911125235-30813b010e3a | 11 Sep 2024 | none | Apache-2.0 | — | Details → |
| v2.0.3-0.20240903205035-ec2eb71df70a | 03 Sep 2024 | none | Apache-2.0 | — | Details → |
| v2.0.2 | 16 Jul 2024 | none | Apache-2.0 | — | Details → |
| v2.0.0-20240703124230-eaad265011d6 | 03 Jul 2024 | none | Apache-2.0 | — | Details → |
| v2.0.0-20240629135448-09bd8d4d1c12 | 29 Jun 2024 | none | Apache-2.0 | — | Details → |
| v2.0.1 | 24 Jun 2024 | none | Apache-2.0 | — | Details → |
| v2.0.0 | 19 Jun 2024 | none | Apache-2.0 | — | Details → |
| v2.0.6-testnet | 10 May 2024 | none | Apache-2.0 | — | Details → |
| v2.0.5-testnet.0.20240320202519-60bf17b13675 | 20 Mar 2024 | none | Apache-2.0 | — | Details → |
| v2.0.5-testnet.0.20240306023503-dc4c1de60df5 | 06 Mar 2024 | none | Apache-2.0 | — | Details → |
| v2.0.5-testnet | 23 Feb 2024 | none | Apache-2.0 | — | Details → |
| v2.0.4-testnet | 21 Feb 2024 | none | Apache-2.0 | — | Details → |
| v2.0.3-testnet | 21 Feb 2024 | none | Apache-2.0 | — | Details → |
| v2.0.1-testnet.0.20240220131156-cbc7ea2f3d09 | 20 Feb 2024 | none | Apache-2.0 | — | Details → |
| v2.0.2-testnet | 20 Feb 2024 | none | Apache-2.0 | — | Details → |
| v2.0.1-testnet | 10 Jan 2024 | none | Apache-2.0 | — | Details → |
| v2.0.0-testnet | 10 Jan 2024 | none | Apache-2.0 | — | Details → |
All 39 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/drand/drand/v2
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/drand/drand/v2
Is github.com/drand/drand/v2 safe to use?
Vulert has no vulnerabilities on record for github.com/drand/drand/v2 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/drand/drand/v2's Vulert package health score?
Vulert scores github.com/drand/drand/v2 83/100, which reads as in good shape. 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/drand/drand/v2 affected?
No. v2.1.8, 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/drand/drand/v2 should I use?
v2.1.8 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/drand/drand/v2 have?
0 vulnerabilities are recorded for github.com/drand/drand/v2 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/drand/drand/v2 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/drand/drand/v2 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/drand/drand/v2 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/drand/drand/v2 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/drand/drand/v2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.