VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/cncf/udpa/go: vulnerability history, versions and safety

github.com/cncf/udpa/go 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.

See all github.com/cncf/udpa/go vulnerabilities

Vulert verdict on github.com/cncf/udpa/go v0.0.0-20220112060539-c52dc94e7fbe i

Updated on 23 Oct 2026

Good news: v0.0.0-20220112060539-c52dc94e7fbe, the version you would install today, has no known vulnerabilities.

Package health score 45/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Niche
  • Community Quiet

The registry marks the latest release as deprecated, which caps this score.

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

  • Current release v0.0.0-20220112060539-c52dc94e7fbe — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 234 i
  • OpenSSF scorecard 2/10 i
  • Last release 57 months ago i
  • Licence Apache-2.0 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/cncf/udpa/go, 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
v0.0.0-20220112060539-c52dc94e7fbe 12 Jan 2022 none Apache-2.0 — Details →
v0.0.0-20210930031921-04548b0d99d4 30 Sep 2021 none Apache-2.0 — Details →
v0.0.0-20210322005330-6414d713912e 22 Mar 2021 none Apache-2.0 — Details →
v0.0.0-20210210032658-bff43e8824d0 10 Feb 2021 none Apache-2.0 — Details →
v0.0.0-20201211205326-cc1b757b3edd 11 Dec 2020 none Apache-2.0 — Details →
v0.0.0-20201120205902-5459f2c99403 20 Nov 2020 none Apache-2.0 — Details →
v0.0.0-20201120164455-82be644d481c 20 Nov 2020 none Apache-2.0 — Details →
v0.0.0-20201120155756-a08826d251c4 20 Nov 2020 none Apache-2.0 — Details →
v0.0.0-20201119205042-3a44e3262f66 19 Nov 2020 none Apache-2.0 — Details →
v0.0.0-20201001150855-7e6fe0510fb5 01 Oct 2020 none Apache-2.0 — Details →
v0.0.0-20200909154343-1f710aca26a9 09 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20200903234907-e9e5d2bce62f 03 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20200629203442-efcf912fb354 29 Jun 2020 none Apache-2.0 — Details →
v0.0.0-20200624233733-ca580c4fcf87 24 Jun 2020 none Apache-2.0 — Details →
v0.0.0-20200508205342-3b31d022a144 08 May 2020 none Apache-2.0 — Details →
v0.0.0-20200327203949-e8cd3a4bb307 27 Mar 2020 none Apache-2.0 — Details →
v0.0.0-20200324003616-bae28a880fdb 24 Mar 2020 none Apache-2.0 — Details →
v0.0.0-20200313221541-5f7e5dd04533 13 Mar 2020 none Apache-2.0 — Details →
v0.0.0-20200124205748-db4b343e48c1 24 Jan 2020 none Apache-2.0 — Details →
v0.0.0-20191230090109-edbea6a78f6d 30 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191224132323-b0644318a8ba 24 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191223164906-f4306cbaebf0 23 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191212200710-89624d5efc54 12 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191209042840-269d4d468f6f 09 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191209041436-4aa8bb1beff1 09 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191206231327-369acd9ff1dd 06 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191206230902-d1f2ba7f5ba6 06 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191206122238-e7e8174810bf 06 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191204024617-dd32ff4d2071 04 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191202223742-a45f15447161 02 Dec 2019 none Apache-2.0 — Details →
v0.0.0-20191127193423-5f054cc4b1a0 27 Nov 2019 none Apache-2.0 — Details →

All 31 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/cncf/udpa/go

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/cncf/udpa/go

Is github.com/cncf/udpa/go safe to use?

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

Vulert scores github.com/cncf/udpa/go 45/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of github.com/cncf/udpa/go affected?

No. v0.0.0-20220112060539-c52dc94e7fbe, 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/cncf/udpa/go should I use?

v0.0.0-20210322005330-6414d713912e 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/cncf/udpa/go have?

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

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

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