Vulnerability Database · Go · Package report
github.com/alitto/pond: vulnerability history, versions and safety
github.com/alitto/pond 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/alitto/pond v1.9.2 i
Updated on 23 Oct 2026
Good news: v1.9.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on v1.9.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.9.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.9.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 2,200 i
- OpenSSF scorecard 3/10 i
- Last release 25 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/alitto/pond, 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-20240901143333-18002c10fedb 01 Sep 2024
- v1.9.2 01 Sep 2024
- v1.9.2-0.20240901143333-18002c10fedb 01 Sep 2024
- v1.9.2-0.20240829112924-7f4c992eddaa 29 Aug 2024
- v1.9.1 10 Jul 2024
- v1.9.1-0.20240710122324-5f162d4380e6 10 Jul 2024
- v0.0.0-20240617160249-e2fe4156b86c 17 Jun 2024
- v1.8.4-0.20240617160249-e2fe4156b86c 17 Jun 2024
- v1.9.0 17 Jun 2024
- v1.8.4-0.20240608214235-3f439a7c5bd4 08 Jun 2024
- v0.0.0-20240314182146-b9d24f45ffcd 14 Mar 2024
- v1.8.4-0.20240314182146-b9d24f45ffcd 14 Mar 2024
- v1.8.4-0.20240313212801-26c8dbee8d0e 13 Mar 2024
- v0.0.0-20230423213019-f1f46f02a68f 23 Apr 2023
- v1.8.4-0.20230423213019-f1f46f02a68f 23 Apr 2023
- v1.8.4-0.20230225121325-4f20b4cc1f2f 25 Feb 2023
- v1.8.4-0.20230225071530-2516a997cdfb 25 Feb 2023
- v1.8.4-0.20230215113541-c2975b2facde 15 Feb 2023
- v1.8.3 31 Jan 2023
- v1.8.2 14 Oct 2022
- v1.8.2-0.20221013115032-7a514efd0199 13 Oct 2022
- v1.8.1 28 Aug 2022
- v1.8.1-0.20220822111040-d01340a7a21e 22 Aug 2022
- v1.8.1-0.20220822042147-35de043ccc0c 22 Aug 2022
- v1.8.1-0.20220731144555-7a99f8514bc0 31 Jul 2022
- v1.8.0 09 May 2022
- v0.0.0-20220409144041-d4c09d4973f9 09 Apr 2022
- v1.7.2 09 Apr 2022
- v1.7.2-0.20220409144041-d4c09d4973f9 09 Apr 2022
- v0.0.0-20220312204247-286125ed9e00 12 Mar 2022
- v1.7.1 12 Mar 2022
- v1.7.1-0.20220312121037-23a42e4bedbe 12 Mar 2022
- v1.7.1-0.20220307102212-fe39f934963a 07 Mar 2022
- v1.7.1-0.20220306225036-5a66a00af99c 06 Mar 2022
- v1.7.0 02 Jan 2022
- v1.6.2-0.20211226135010-9d7bd8fe088e 26 Dec 2021
- v1.6.1 26 Dec 2021
- v1.6.1-0.20211225235746-61e1a00a7647 25 Dec 2021
- v1.6.0 20 Nov 2021
- v1.5.1 10 Jul 2021
- v1.5.1-0.20210429120923-72559da49da6 29 Apr 2021
- v1.5.0 31 Dec 2020
- v1.4.1-0.20201231173129-5b374210cb36 31 Dec 2020
- v1.4.0 07 Jun 2020
- v1.3.1-0.20200531182255-f8b427ec5a7b 31 May 2020
- v1.3.0 26 May 2020
- v0.0.0-20200403120900-349c5aa212b7 03 Apr 2020
- v1.2.1-0.20200403120900-349c5aa212b7 03 Apr 2020
- v1.2.0 31 Mar 2020
- v1.1.0 31 Mar 2020
- v0.0.0-20200329134648-98e553d83c54 29 Mar 2020
- v1.0.0 29 Mar 2020
- v0.0.0-20200328212536-de7514db303f 28 Mar 2020
- v0.0.0-20200328212143-b7bf7d7cea75 28 Mar 2020
- v0.0.0-20200328140845-2664f1bbde39 28 Mar 2020
- v0.0.0-20200324184958-7b9b533e58b9 24 Mar 2020
- v0.0.0-20200321145758-8ab3413ad226 21 Mar 2020
All 57 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/alitto/pond
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/alitto/pond
Is github.com/alitto/pond safe to use?
Vulert has no vulnerabilities on record for github.com/alitto/pond 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/alitto/pond's Vulert package health score?
Vulert scores github.com/alitto/pond 66/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/alitto/pond affected?
No. v1.9.2, 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/alitto/pond should I use?
v1.9.2 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/alitto/pond have?
0 vulnerabilities are recorded for github.com/alitto/pond 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/alitto/pond vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/alitto/pond 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/alitto/pond 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/alitto/pond for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/alitto/pond version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.