Vulnerability Database · Go · Package report

github.com/alitto/pond/v2: vulnerability history, versions and safety

github.com/alitto/pond/v2 is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/alitto/pond/v2 v2.7.3 i

Updated on 23 Oct 2026

Good news: v2.7.3, the version you would install today, has no known vulnerabilities.

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

What to do: Stay on v2.7.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v2.7.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v2.7.3 — 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 this month 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/v2, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v2.7.4-0.20261017214818-52d217871448 17 Oct 2026 none MIT — Details →
v2.7.3 17 Oct 2026 none MIT — Details →
v2.7.2 03 Oct 2026 none MIT — Details →
v2.7.1 14 Apr 2026 none MIT — Details →
v2.7.0 06 Mar 2026 none MIT — Details →
v2.6.2 16 Feb 2026 none MIT — Details →
v2.6.1-0.20260216002700-642bffaecd6f 16 Feb 2026 none MIT — Details →
v2.6.1 16 Feb 2026 none MIT — Details →
v2.0.0-20251125144531-505910b3f0a6 25 Nov 2025 none MIT — Details →
v2.6.0 25 Nov 2025 none MIT — Details →
v2.5.1-0.20250821114400-de8edd9ccd6b 21 Aug 2025 none MIT — Details →
v2.5.0 13 Jul 2025 none MIT — Details →
v2.4.0 20 Jun 2025 none MIT — Details →
v2.3.4 20 Apr 2025 none MIT — Details →
v2.3.4-0.20250416134735-5cc70c2c81e8 16 Apr 2025 none MIT — Details →
v2.3.3 16 Apr 2025 none MIT — Details →
v2.3.2 04 Apr 2025 none MIT — Details →
v2.3.1 03 Apr 2025 none MIT — Details →
v2.3.0 23 Mar 2025 none MIT — Details →
v2.2.1-0.20250217004132-e2470f0daae6 17 Feb 2025 none MIT — Details →
v2.2.0 17 Feb 2025 none MIT — Details →
v2.1.6 25 Dec 2024 none MIT — Details →
v2.1.6-0.20241212150859-ac7c6a3bfdb5 12 Dec 2024 none MIT — Details →
v2.1.6-0.20241203105529-33005d126724 03 Dec 2024 none MIT — Details →
v2.1.5 27 Nov 2024 none MIT — Details →
v2.1.5-0.20241127145438-d45599396ea4 27 Nov 2024 none MIT — Details →
v2.1.5-0.20241115232721-fc408b5e8b5e 15 Nov 2024 none MIT — Details →
v2.1.4 15 Nov 2024 none MIT — Details →
v2.1.3 13 Nov 2024 none MIT — Details →
v2.1.3-0.20241113150116-9f8d16a02396 13 Nov 2024 none MIT — Details →
v2.1.2 13 Nov 2024 none MIT — Details →
v2.1.1 10 Nov 2024 none MIT — Details →
v2.1.1-0.20241110214831-f1d2a440315f 10 Nov 2024 none MIT — Details →
v2.0.5-0.20241109143020-11ecf7052c2e 09 Nov 2024 none MIT — Details →
v2.1.0 09 Nov 2024 none MIT — Details →
v2.0.4 29 Oct 2024 none MIT — Details →
v2.0.4-0.20241029113943-12d1782ceada 29 Oct 2024 none MIT — Details →
v2.0.3 24 Oct 2024 none MIT — Details →
v2.0.3-0.20241024142041-1e2825016c4d 24 Oct 2024 none MIT — Details →
v2.0.2 21 Oct 2024 none MIT — Details →
v2.0.2-0.20241021220707-af6a9cbe7131 21 Oct 2024 none MIT — Details →
v2.0.2-0.20241020180044-e6af32e09afb 20 Oct 2024 none MIT — Details →
v2.0.1 20 Oct 2024 none MIT — Details →
v2.0.1-0.20241020142349-bea3bad15eba 20 Oct 2024 none MIT — Details →
v2.0.1-0.20241020010449-df504463c5e9 20 Oct 2024 none MIT — Details →
v2.0.1-0.20241020005849-3d001a9f9bc9 20 Oct 2024 none MIT — Details →
v2.0.0 20 Oct 2024 none MIT — Details →

All 47 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/v2

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/alitto/pond/v2

Is github.com/alitto/pond/v2 safe to use?

Vulert has no vulnerabilities on record for github.com/alitto/pond/v2 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/v2's Vulert package health score?

Vulert scores github.com/alitto/pond/v2 81/100, which reads as in good shape. 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/v2 affected?

No. v2.7.3, 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.

How many vulnerabilities does github.com/alitto/pond/v2 have?

0 vulnerabilities are recorded for github.com/alitto/pond/v2 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/v2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/alitto/pond/v2 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/v2 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/v2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/alitto/pond/v2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.