Vulnerability Database · Go · Package report

github.com/DataDog/viper: vulnerability history, versions and safety

github.com/DataDog/viper 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/DataDog/viper v1.15.3 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v1.15.3 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 3 i
  • OpenSSF scorecard 4/10 i
  • Last release 4 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/DataDog/viper, 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.15.4-0.20260707134002-b93dd4f91de5 07 Jul 2026 none MIT — Details →
v1.15.3 17 Jun 2026 none MIT — Details →
v1.15.2 15 Jun 2026 none MIT — Details →
v1.15.2-0.20260326144059-a2419321258a 26 Mar 2026 none MIT — Details →
v1.15.1 20 Feb 2026 none MIT — Details →
v1.14.1-0.20251201094110-03e20a5a2419 01 Dec 2025 none MIT — Details →
v1.15.0 01 Dec 2025 none MIT — Details →
v1.14.1-0.20251117172501-5b5dc463bad3 17 Nov 2025 none MIT — Details →
v1.14.1-0.20251008075154-b33ffa9792d9 08 Oct 2025 none MIT — Details →
v1.14.1-0.20251007075245-0ae370c4b458 07 Oct 2025 none MIT — Details →
v1.14.1-0.20251007072727-5a2ac1ff821e 07 Oct 2025 none MIT — Details →
v1.14.1-0.20251006115257-6f006369de25 06 Oct 2025 none MIT — Details →
v1.14.1-0.20251002211519-52225e3aeac8 02 Oct 2025 none MIT — Details →
v1.14.1-0.20250903173614-ea950efef2e1 03 Sep 2025 none MIT — Details →
v1.14.1-0.20250903173133-55b36af9db59 03 Sep 2025 none MIT — Details →
v0.0.0-20250827205637-0540d4806273 27 Aug 2025 none MIT — Details →
v1.14.1-0.20250827205637-0540d4806273 27 Aug 2025 none MIT — Details →
v0.0.0-20250612143030-1b15c8822ed4 12 Jun 2025 none MIT — Details →
v1.14.1-0.20250612143030-1b15c8822ed4 12 Jun 2025 none MIT — Details →
v1.14.1-0.20250128143513-2e392e9ceee3 28 Jan 2025 none MIT — Details →
v1.14.1-0.20250128103558-9e75b5cbf5b0 28 Jan 2025 none MIT — Details →
v1.14.1-0.20250127231111-027880b05ba1 27 Jan 2025 none MIT — Details →
v1.14.1-0.20250127172929-eef46d1fc5ce 27 Jan 2025 none MIT — Details →
v1.14.0 10 Dec 2024 none MIT — Details →
v1.13.6-0.20240827151044-7aae2e19172f 27 Aug 2024 none MIT — Details →
v1.13.5 29 May 2024 none MIT — Details →
v1.13.5-0.20240529152645-537f03e453bf 29 May 2024 none MIT — Details →
v1.13.4 28 May 2024 none MIT — Details →
v1.13.4-0.20240528134254-c4cf4fd691ed 28 May 2024 none MIT — Details →
v1.13.3 20 May 2024 none MIT — Details →
v1.13.3-0.20240520144841-89890a76dece 20 May 2024 none MIT — Details →
v1.13.3-0.20240430093604-ab6329b19a68 30 Apr 2024 none MIT — Details →
v1.13.3-0.20240429123956-163dcbf55ffc 29 Apr 2024 none MIT — Details →
v1.13.3-0.20240429100011-21ba0b3675ac 29 Apr 2024 none MIT — Details →
v1.13.3-0.20240429091617-a3402cd855a0 29 Apr 2024 none MIT — Details →
v1.13.3-0.20240426154822-ee42f58c545e 26 Apr 2024 none MIT — Details →
v1.13.3-0.20240426152054-f8876cb83d1a 26 Apr 2024 none MIT — Details →
v1.13.3-0.20240426134232-ad820bb7e16d 26 Apr 2024 none MIT — Details →
v1.13.2 25 Apr 2024 none MIT — Details →
v1.13.1 22 Apr 2024 none MIT — Details →
v1.12.1-0.20240311110542-3e7837fd388f 11 Mar 2024 none MIT — Details →
v1.13.0 11 Mar 2024 none MIT — Details →
v1.12.1-0.20230929131643-1d9194ffabeb 29 Sep 2023 none MIT — Details →
v1.12.0 02 Sep 2022 none MIT — Details →
v1.11.1-0.20220902165409-2801bd720205 02 Sep 2022 none MIT — Details →
v1.11.0 13 Jul 2022 none MIT — Details →
v1.10.1-0.20220531084908-7e5da050b17a 31 May 2022 none MIT — Details →
v1.10.0 10 May 2022 none MIT — Details →
v1.9.1-0.20220509135910-0b35ab449316 09 May 2022 none MIT — Details →
v1.9.1-0.20220509130951-da54697d4620 09 May 2022 none MIT — Details →
v1.9.1-0.20220509113123-cd67cbfef979 09 May 2022 none MIT — Details →
v1.9.1-0.20220509112831-4ad72c7943ff 09 May 2022 none MIT — Details →
v1.9.1-0.20220509111933-6dfa47233ab6 09 May 2022 none MIT — Details →
v1.9.1-0.20220421173204-3791d10ad196 21 Apr 2022 none MIT — Details →
v1.9.1-0.20220420201201-88367e374b0e 20 Apr 2022 none MIT — Details →
v1.9.1-0.20220420104439-80234a08d300 20 Apr 2022 none MIT — Details →
v1.9.1-0.20220420104439-dd14d2c73f2d 20 Apr 2022 none MIT — Details →
v1.9.1-0.20220217171657-1cc3fa065c3e 17 Feb 2022 none MIT — Details →
v0.0.0-20210720152930-8e7459bcf337 20 Jul 2021 none MIT — Details →
v1.9.1-0.20210720152930-8e7459bcf337 20 Jul 2021 none MIT — Details →
v1.8.1-0.20201112231441-af23aee54ecc 12 Nov 2020 none MIT — Details →
v1.9.0 12 Nov 2020 none MIT — Details →
v1.8.1-0.20201111182851-76228697183b 11 Nov 2020 none MIT — Details →
v1.8.0 14 Sep 2020 none MIT — Details →
v1.7.1 27 Feb 2020 none MIT — Details →
v1.7.1-0.20200227155142-7d500a2af36e 27 Feb 2020 none MIT — Details →
v1.0.3 28 Sep 2018 none MIT — Details →
v1.1.1 28 Sep 2018 none MIT — Details →
v1.1.0 03 Aug 2018 none MIT — Details →
v1.0.2 19 Mar 2018 none MIT — Details →
v1.0.1 19 Mar 2018 none MIT — Details →
v1.0.0 23 Jul 2017 none MIT — Details →
v0.0.0-20150414181502-ba3382dd238f 14 Apr 2015 none MIT — Details →

All 73 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/DataDog/viper

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/DataDog/viper

Is github.com/DataDog/viper safe to use?

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

Vulert scores github.com/DataDog/viper 65/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/DataDog/viper affected?

No. v1.15.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.

Which version of github.com/DataDog/viper should I use?

v1.15.3 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/DataDog/viper have?

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

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

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