Vulnerability Database · Go · Package report

github.com/libdns/libdns: vulnerability history, versions and safety

github.com/libdns/libdns 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/libdns/libdns v1.1.1 i

Updated on 23 Oct 2026

Good news: v1.1.1, the version you would install today, has no known vulnerabilities.

Package health score 63/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release v1.1.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 460 i
  • OpenSSF scorecard 2/10 i
  • Last release 14 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/libdns/libdns, 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
v1.2.0-alpha.1.0.20260625195721-43599001f01c 25 Jun 2026 none MIT — Details →
v1.2.0-alpha.1.0.20260128175948-d3609c6996e6 28 Jan 2026 none MIT — Details →
v1.2.0-alpha.1.0.20260119000127-25ab11753577 19 Jan 2026 none MIT — Details →
v1.2.0-alpha.1.0.20260116164919-a414e09927b8 16 Jan 2026 none MIT — Details →
v1.2.0-alpha.1.0.20250917210354-fce8af8a49e7 17 Sep 2025 none MIT — Details →
v1.2.0-alpha.1.0.20250913035451-da352cac42d0 13 Sep 2025 none MIT — Details →
v1.1.2-0.20250911212231-e35e5b2a2609 11 Sep 2025 none MIT — Details →
v1.2.0-alpha.1 11 Sep 2025 none MIT — Details →
v1.1.2-0.20250911212132-3fe12606831b 11 Sep 2025 none MIT — Details →
v1.1.2-0.20250902201857-634fd1b44915 02 Sep 2025 none MIT — Details →
v1.1.1 13 Aug 2025 none MIT — Details →
v1.1.1-0.20250813152926-6071c1f4fbaa 13 Aug 2025 none MIT — Details →
v1.1.1-0.20250609181447-6ab812eb6061 09 Jun 2025 none MIT — Details →
v1.0.1-0.20250506230618-6be57668e7bf 06 May 2025 none MIT — Details →
v1.1.0 06 May 2025 none MIT — Details →
v1.0.1-0.20250505145637-933c3901a633 05 May 2025 none MIT — Details →
v1.0.0 28 Apr 2025 none MIT — Details →
v1.0.0-beta.1.0.20250423132730-e0df105aed0e 23 Apr 2025 none MIT — Details →
v1.0.0-beta.1.0.20250420133940-10a2b0b2c222 20 Apr 2025 none MIT — Details →
v1.0.0-beta.1.0.20250419133011-db2a2dd0747a 19 Apr 2025 none MIT — Details →
v1.0.0-beta.1.0.20250419132927-8fedb4f57bfa 19 Apr 2025 none MIT — Details →
v1.0.0-beta.1.0.20250416221626-5ab1d4de259f 16 Apr 2025 none MIT — Details →
v1.0.0-beta.1.0.20250415210212-7fe2177d834c 15 Apr 2025 none MIT — Details →
v1.0.0-beta.1.0.20250407043619-f18b99b48099 07 Apr 2025 none MIT — Details →
v1.0.0-beta.1 07 Apr 2025 none MIT — Details →
v0.2.4-0.20250407022646-1cd79c4a54f0 07 Apr 2025 none MIT — Details →
v0.2.4-0.20250328071820-1e63e0275455 28 Mar 2025 none MIT — Details →
v0.2.4-0.20250325234213-92199907683f 25 Mar 2025 none MIT — Details →
v0.2.4-0.20250319223134-9ae37dc28470 19 Mar 2025 none MIT — Details →
v0.0.0-20250315123641-013384db2596 15 Mar 2025 none MIT — Details →
v0.2.4-0.20250315123641-013384db2596 15 Mar 2025 none MIT — Details →
v0.2.4-0.20250311164749-855f0d6e4220 11 Mar 2025 none MIT — Details →
v0.2.3 14 Feb 2025 none MIT — Details →
v0.2.2 21 Mar 2024 none MIT — Details →
v0.2.2-0.20240321181339-8b75c024f21e 21 Mar 2024 none MIT — Details →
v0.2.2-0.20231213153513-6b4e74fc9c11 13 Dec 2023 none MIT — Details →
v0.2.2-0.20230501153445-5344f2e6777e 01 May 2023 none MIT — Details →
v0.2.2-0.20230501153124-da79a691c239 01 May 2023 none MIT — Details →
v0.2.2-0.20230227175549-2dc480633939 27 Feb 2023 none MIT — Details →
v0.2.2-0.20221006221142-3ef90aee33fd 06 Oct 2022 none MIT — Details →
v0.2.2-0.20220921224252-99c19a9c1bac 21 Sep 2022 none MIT — Details →
v0.2.1 26 May 2021 none MIT — Details →
v0.2.1-0.20210526195756-75d1f505ee7f 26 May 2021 none MIT — Details →
v0.0.0-20210224173630-348effc20d6b 24 Feb 2021 none MIT — Details →
v0.2.0 24 Feb 2021 none MIT — Details →
v0.0.0-20200501023120-186724ffc821 01 May 2020 none MIT — Details →
v0.1.0 01 May 2020 none MIT — Details →
v0.0.0-20200501014611-297187ba3fa4 01 May 2020 none MIT — Details →
v0.0.0-20200430215144-323366505021 30 Apr 2020 none MIT — Details →
v0.0.0-20200430170733-54097deaf793 30 Apr 2020 none MIT — Details →
v0.0.0-20200430163404-ee2c42449104 30 Apr 2020 none MIT — Details →
v0.0.0-20200430050049-f0d5b564b6b3 30 Apr 2020 none — — Details →

All 52 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/libdns/libdns

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/libdns/libdns

Is github.com/libdns/libdns safe to use?

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

Vulert scores github.com/libdns/libdns 63/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/libdns/libdns affected?

No. v1.1.1, 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/libdns/libdns should I use?

v1.1.1 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/libdns/libdns have?

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

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

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