Vulnerability Database · Go · Package report
github.com/wlynxg/anet: vulnerability history, versions and safety
github.com/wlynxg/anet 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/wlynxg/anet v0.0.5 i
Updated on 23 Oct 2026
Good news: v0.0.5, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.0.5 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 45 i
- OpenSSF scorecard 1/10 i
- Last release 24 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/wlynxg/anet, 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.6-0.20250109065809-5501d401a269 09 Jan 2025
- v0.0.5 04 Oct 2024
- v0.0.5-0.20241004142225-839bc3a920f1 04 Oct 2024
- v0.0.5-0.20240823004953-a79b5ca41e53 23 Aug 2024
- v0.0.4 06 Aug 2024
- v0.0.4-0.20240806025826-e684438fc7c6 06 Aug 2024
- v0.0.4-0.20240628132737-c6dbd5e3e23f 28 Jun 2024
- v0.0.4-0.20240620073851-a5cc60212c79 20 Jun 2024
- v0.0.3 20 Jun 2024
- v0.0.2 18 Jun 2024
- v0.0.2-0.20240618115830-ace4c224ee11 18 Jun 2024
- v0.0.0-20231020091731-ab437b8f7596 20 Oct 2023
- v0.0.1 20 Oct 2023
- v0.0.0-20230919012416-aa9594d8ec61 19 Sep 2023
- v0.0.0-20230916111621-5930626b8a60 16 Sep 2023
- v0.0.0-20230915143312-ba027ced4d0c 15 Sep 2023
- v0.0.0-20230809092352-2e97b0d4edde 09 Aug 2023
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.6-0.20250109065809-5501d401a269 | 09 Jan 2025 | none | BSD-3-Clause | — | Details → |
| v0.0.5 | 04 Oct 2024 | none | BSD-3-Clause | — | Details → |
| v0.0.5-0.20241004142225-839bc3a920f1 | 04 Oct 2024 | none | BSD-3-Clause | — | Details → |
| v0.0.5-0.20240823004953-a79b5ca41e53 | 23 Aug 2024 | none | BSD-3-Clause | — | Details → |
| v0.0.4 | 06 Aug 2024 | none | BSD-3-Clause | — | Details → |
| v0.0.4-0.20240806025826-e684438fc7c6 | 06 Aug 2024 | none | BSD-3-Clause | — | Details → |
| v0.0.4-0.20240628132737-c6dbd5e3e23f | 28 Jun 2024 | none | BSD-3-Clause | — | Details → |
| v0.0.4-0.20240620073851-a5cc60212c79 | 20 Jun 2024 | none | BSD-3-Clause | — | Details → |
| v0.0.3 | 20 Jun 2024 | none | BSD-3-Clause | — | Details → |
| v0.0.2 | 18 Jun 2024 | none | BSD-3-Clause | — | Details → |
| v0.0.2-0.20240618115830-ace4c224ee11 | 18 Jun 2024 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20231020091731-ab437b8f7596 | 20 Oct 2023 | none | BSD-3-Clause | — | Details → |
| v0.0.1 | 20 Oct 2023 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20230919012416-aa9594d8ec61 | 19 Sep 2023 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20230916111621-5930626b8a60 | 16 Sep 2023 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20230915143312-ba027ced4d0c | 15 Sep 2023 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20230809092352-2e97b0d4edde | 09 Aug 2023 | none | BSD-3-Clause | — | Details → |
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/wlynxg/anet
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/wlynxg/anet
Is github.com/wlynxg/anet safe to use?
Vulert has no vulnerabilities on record for github.com/wlynxg/anet 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/wlynxg/anet's Vulert package health score?
Vulert scores github.com/wlynxg/anet 56/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/wlynxg/anet affected?
No. v0.0.5, 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/wlynxg/anet should I use?
v0.0.5 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/wlynxg/anet have?
0 vulnerabilities are recorded for github.com/wlynxg/anet 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/wlynxg/anet vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/wlynxg/anet 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/wlynxg/anet 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/wlynxg/anet for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/wlynxg/anet version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.