Vulnerability Database · Go · Package report
github.com/aead/chacha20: vulnerability history, versions and safety
github.com/aead/chacha20 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/aead/chacha20 v0.0.0-20180709150244-8b13a72661da i
Updated on 23 Oct 2026
Good news: v0.0.0-20180709150244-8b13a72661da, 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-20180709150244-8b13a72661da or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20180709150244-8b13a72661da too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20180709150244-8b13a72661da — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 75 i
- OpenSSF scorecard 1/10 i
- Last release 99 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/aead/chacha20, 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-20180709150244-8b13a72661da 09 Jul 2018
- v0.0.0-20180503225822-e2538746bfea 03 May 2018
- v0.0.0-20180503205305-52db354a4a38 03 May 2018
- v0.0.0-20180426214825-8457f65383c5 26 Apr 2018
- v0.0.0-20180421131426-c1766ed472df 21 Apr 2018
- v0.0.0-20180325213114-e0d4ab3067da 25 Mar 2018
- v0.0.0-20180214104012-c8d29375923a 14 Feb 2018
- v0.0.0-20180214100722-f3ab53f5de6f 14 Feb 2018
- v0.0.0-20170614051014-8d6ce0550041 14 Jun 2017
- v0.0.0-20170221132220-d31a916ded42 21 Feb 2017
- v0.0.0-20161008145849-7e1038a97ad0 08 Oct 2016
- v0.0.0-20160923072723-ba19b6a36496 23 Sep 2016
- v0.0.0-20160909091628-3ec2c68927a4 09 Sep 2016
- v0.0.0-20160819152922-5529e02660c3 19 Aug 2016
- v0.0.0-20160818150540-b9b65edc34d2 18 Aug 2016
- v0.0.0-20160811184921-e33db10901cd 11 Aug 2016
- v0.0.0-20160807172835-86d922430f9b 07 Aug 2016
- v0.0.0-20160807101557-1707b490bb00 07 Aug 2016
- v0.0.0-20160729122410-5f68ba5d50e6 29 Jul 2016
- v0.0.0-20160726182824-b2542acc9b7d 26 Jul 2016
- v0.0.0-20160725212735-b9b9fe0318a2 25 Jul 2016
- v0.0.0-20160725201049-03024572c924 25 Jul 2016
- v0.0.0-20160722195309-8127d1dd8ed5 22 Jul 2016
- v0.0.0-20160722133156-a3756369650e 22 Jul 2016
- v0.0.0-20160720205552-88f11922ed7b 20 Jul 2016
- v0.0.0-20160718202840-f922d5c5aee9 18 Jul 2016
- v0.0.0-20160716195732-9ab4cdea08c2 16 Jul 2016
- v0.0.0-20160714105826-5263d2f04cca 14 Jul 2016
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/aead/chacha20
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/aead/chacha20
Is github.com/aead/chacha20 safe to use?
Vulert has no vulnerabilities on record for github.com/aead/chacha20 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/aead/chacha20's Vulert package health score?
Vulert scores github.com/aead/chacha20 49/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/aead/chacha20 affected?
No. v0.0.0-20180709150244-8b13a72661da, 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/aead/chacha20 should I use?
v0.0.0-20180709150244-8b13a72661da 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/aead/chacha20 have?
0 vulnerabilities are recorded for github.com/aead/chacha20 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/aead/chacha20 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/aead/chacha20 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/aead/chacha20 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/aead/chacha20 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/aead/chacha20 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.