Vulnerability Database · Go · Package report
github.com/hdevalence/ed25519consensus: vulnerability history, versions and safety
github.com/hdevalence/ed25519consensus 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.
See all github.com/hdevalence/ed25519consensus vulnerabilities
Vulert verdict on github.com/hdevalence/ed25519consensus v0.2.0 i
Updated on 23 Oct 2026
Good news: v0.2.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Niche
- Community Inactive
What to do: Stay on v0.2.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.2.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.2.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 52 i
- OpenSSF scorecard 2/10 i
- Last release 33 months ago i
- Licence BSD-3-Clause 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/hdevalence/ed25519consensus, 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.1.1-0.20240118173727-15731de461e4 18 Jan 2024
- v0.2.0 18 Jan 2024
- v0.0.0-20231208232057-d8a485ddd714 08 Dec 2023
- v0.1.1-0.20231208232057-d8a485ddd714 08 Dec 2023
- v0.1.1-0.20231208231351-97fc3202fecb 08 Dec 2023
- v0.1.0 11 Sep 2022
- v0.0.0-20220222234857-c00d1f31bab3 22 Feb 2022
- v0.0.0-20210430192048-0962ce16b305 30 Apr 2021
- v0.0.0-20210204194344-59a8610d2b87 04 Feb 2021
- v0.0.0-20210202233638-329f984e263d 02 Feb 2021
- v0.0.0-20201207055737-7fde80a9d5ff 07 Dec 2020
- v0.0.0-20201204200618-7d6b64986c2c 04 Dec 2020
- v0.0.0-20200813231810-1694d75e712a 13 Aug 2020
- v0.0.0-20200730154435-2455bd97e3c1 30 Jul 2020
- v0.0.0-20200728015710-60ec8d081b84 28 Jul 2020
- v0.0.0-20200727220304-074a83ff54e4 27 Jul 2020
All 16 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/hdevalence/ed25519consensus
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/hdevalence/ed25519consensus
Is github.com/hdevalence/ed25519consensus safe to use?
Vulert has no vulnerabilities on record for github.com/hdevalence/ed25519consensus 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/hdevalence/ed25519consensus's Vulert package health score?
Vulert scores github.com/hdevalence/ed25519consensus 55/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/hdevalence/ed25519consensus affected?
No. v0.2.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/hdevalence/ed25519consensus should I use?
v0.2.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/hdevalence/ed25519consensus have?
0 vulnerabilities are recorded for github.com/hdevalence/ed25519consensus 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/hdevalence/ed25519consensus vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/hdevalence/ed25519consensus 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/hdevalence/ed25519consensus 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/hdevalence/ed25519consensus for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/hdevalence/ed25519consensus version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.