Vulnerability Database · Go · Package report
github.com/agl/ed25519: vulnerability history, versions and safety
github.com/agl/ed25519 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/agl/ed25519 v0.0.0-20200225211852-fd4d107ace12 i
Updated on 23 Oct 2026
Good news: v0.0.0-20200225211852-fd4d107ace12, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v0.0.0-20200225211852-fd4d107ace12 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20200225211852-fd4d107ace12 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20200225211852-fd4d107ace12 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 187 i
- OpenSSF scorecard 0/10 i
- Last release 79 months ago 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/agl/ed25519, 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.0-20200225211852-fd4d107ace12 25 Feb 2020
- v0.0.0-20170116200512-5312a6153412 16 Jan 2017
- v0.0.0-20170116195338-33e7db2c69e7 16 Jan 2017
- v0.0.0-20150830182803-278e1ec8e8a6 30 Aug 2015
- v0.0.0-20150830182803-446061e2131e 30 Aug 2015
- v0.0.0-20150826220904-235aa498686d 26 Aug 2015
- v0.0.0-20150826220904-550d88df8d24 26 Aug 2015
- v0.0.0-20150826220904-92dd82d23b0a 26 Aug 2015
- v0.0.0-20150826220904-bb5ca2006d0a 26 Aug 2015
- v0.0.0-20150826204351-2c9297c0029a 26 Aug 2015
- v0.0.0-20150508133615-2b8e3036fb03 08 May 2015
- v0.0.0-20140907235247-d2b94fd789ea 07 Sep 2014
- v0.0.0-20140215153327-c4161f4c7483 15 Feb 2014
- v0.0.0-20131225135013-f5d0dc54cc35 25 Dec 2013
- v0.0.0-20131222171547-8f60da0a969a 22 Dec 2013
- v0.0.0-20130902155339-5613cf01b3df 02 Sep 2013
- v0.0.0-20121006235732-4117a04a6c31 06 Oct 2012
All 17 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/agl/ed25519
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/agl/ed25519
Is github.com/agl/ed25519 safe to use?
Vulert has no vulnerabilities on record for github.com/agl/ed25519 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/agl/ed25519's Vulert package health score?
Vulert scores github.com/agl/ed25519 47/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/agl/ed25519 affected?
No. v0.0.0-20200225211852-fd4d107ace12, 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/agl/ed25519 should I use?
v0.0.0-20200225211852-fd4d107ace12 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/agl/ed25519 have?
0 vulnerabilities are recorded for github.com/agl/ed25519 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/agl/ed25519 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/agl/ed25519 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/agl/ed25519 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/agl/ed25519 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/agl/ed25519 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.