VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/bufbuild/protoplugin: vulnerability history, versions and safety

github.com/bufbuild/protoplugin 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/bufbuild/protoplugin vulnerabilities

Vulert verdict on github.com/bufbuild/protoplugin v0.0.0-20260414125817-25d1d281b46b i

Updated on 23 Oct 2026

Good news: v0.0.0-20260414125817-25d1d281b46b, the version you would install today, has no known vulnerabilities.

Package health score 63/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.0-20260414125817-25d1d281b46b — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 39 i
  • OpenSSF scorecard 3/10 i
  • Last release 6 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/bufbuild/protoplugin, 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-20260414125817-25d1d281b46b 14 Apr 2026 none Apache-2.0 — Details →
v0.0.0-20250218205857-750e09ce93e1 18 Feb 2025 none Apache-2.0 — Details →
v0.0.0-20250106231243-3a819552c9d9 06 Jan 2025 none Apache-2.0 — Details →
v0.0.0-20241217222811-4b0149c5d99d 17 Dec 2024 none Apache-2.0 — Details →
v0.0.0-20240911180120-7bb73e41a54a 11 Sep 2024 none Apache-2.0 — Details →
v0.0.0-20240910161437-27b7a335254b 10 Sep 2024 none Apache-2.0 — Details →
v0.0.0-20240905132716-da0a912590f3 05 Sep 2024 none Apache-2.0 — Details →
v0.0.0-20240323223605-e2735f6c31ee 23 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240323223305-402cf9d72c7f 23 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240319191650-d3a3f51a49d3 19 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240318153824-eeb4e72439df 18 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240318150527-47202a244e13 18 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240318142856-6e44effc82f8 18 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240317230703-1de7ea8b25db 17 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240317212733-3936c517373c 17 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240317211504-2aff7b20cf7d 17 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240307214627-634912f18796 07 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240307132113-43fa23ac5a11 07 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240306230112-607d06e9be64 06 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240306172645-67b4208e5ac4 06 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240305195756-bc4d0fda2022 05 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240305191028-6ede8e740d8c 05 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240305183229-b1da5156395c 05 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240305182532-d9e34368afc8 05 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240304043046-10539905c261 04 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240304040433-bae201053f1d 04 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240304023125-79b00362b3a6 04 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240304014227-f223137c2e28 04 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240304010213-a9baf3679a59 04 Mar 2024 none Apache-2.0 — Details →

All 29 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/bufbuild/protoplugin

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/bufbuild/protoplugin

Is github.com/bufbuild/protoplugin safe to use?

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

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

No. v0.0.0-20260414125817-25d1d281b46b, 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/bufbuild/protoplugin should I use?

v0.0.0-20260414125817-25d1d281b46b 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/bufbuild/protoplugin have?

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

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

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