Vulnerability Database · Go · Package report

github.com/devtron-labs/protos: vulnerability history, versions and safety

github.com/devtron-labs/protos 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/devtron-labs/protos v0.0.2 i

Updated on 23 Oct 2026

Good news: v0.0.2, the version you would install today, has no known vulnerabilities.

Package health score 59/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1 i
  • Last release 36 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/devtron-labs/protos, 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.3-0.20250323220609-ecf8a0f7305e 23 Mar 2025 none Apache-2.0 — Details →
v0.0.3-0.20240912111807-605886d90b8d 12 Sep 2024 none Apache-2.0 — Details →
v0.0.3-0.20240809072909-83171af34169 09 Aug 2024 none Apache-2.0 — Details →
v0.0.3-0.20240802105333-92ee9bb85d80 02 Aug 2024 none Apache-2.0 — Details →
v0.0.3-0.20240726131238-dff2574e623d 26 Jul 2024 none Apache-2.0 — Details →
v0.0.3-0.20240726064057-dd2990c91e41 26 Jul 2024 none Apache-2.0 — Details →
v0.0.3-0.20240627063800-0a2d7a56b10e 27 Jun 2024 none Apache-2.0 — Details →
v0.0.3-0.20240527113333-08a3be5ec6c1 27 May 2024 none Apache-2.0 — Details →
v0.0.3-0.20240527105616-2ad3af9c4244 27 May 2024 none Apache-2.0 — Details →
v0.0.3-0.20240527103558-5ea1d0bdc33c 27 May 2024 none Apache-2.0 — Details →
v0.0.3-0.20240527094010-d0707219a026 27 May 2024 none Apache-2.0 — Details →
v0.0.3-0.20240326053929-48e42d9d4534 26 Mar 2024 none Apache-2.0 — Details →
v0.0.3-0.20240206121238-3a06730397b7 06 Feb 2024 none Apache-2.0 — Details →
v0.0.3-0.20240130061723-7b2e12ab0abb 30 Jan 2024 none Apache-2.0 — Details →
v0.0.1-beta3.0.20231011053614-cc147fc08406 11 Oct 2023 none Apache-2.0 — Details →
v0.0.2 11 Oct 2023 none Apache-2.0 — Details →
v0.0.1-beta2.0.20230929065359-439da8b342b9 29 Sep 2023 none Apache-2.0 — Details →
v0.0.1-beta3 29 Sep 2023 none Apache-2.0 — Details →
v0.0.0-20230929064139-55bee4f4fdc1 29 Sep 2023 none Apache-2.0 — Details →
v0.0.0-20230929062356-94b1adfb041b 29 Sep 2023 none Apache-2.0 — Details →
v0.0.1-beta2 29 Sep 2023 none Apache-2.0 — Details →
v0.0.0-20230503113602-282404f70fd2 03 May 2023 none Apache-2.0 — Details →
v0.0.0-20230307051313-ecb763b443a8 07 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230306074100-0c6d80ec3e05 06 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230306071754-ace08ea8f902 06 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230303111945-adc9e998b712 03 Mar 2023 none Apache-2.0 — Details →

All 26 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/devtron-labs/protos

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/devtron-labs/protos

Is github.com/devtron-labs/protos safe to use?

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

Vulert scores github.com/devtron-labs/protos 59/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/devtron-labs/protos affected?

No. v0.0.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/devtron-labs/protos should I use?

v0.0.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/devtron-labs/protos have?

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

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

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