Vulnerability Database · Go · Package report

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

github.com/kubepug/kubepug 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/kubepug/kubepug v1.7.1 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release v1.7.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,842 i
  • OpenSSF scorecard 4/10 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/kubepug/kubepug, 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.7.2-0.20260330104633-5a18f77bbd6c 30 Mar 2026 none Apache-2.0 — Details →
v1.7.2-0.20241231105121-0b5873803e92 31 Dec 2024 none Apache-2.0 — Details →
v1.7.2-0.20241216094719-0807809ae79b 16 Dec 2024 none Apache-2.0 — Details →
v1.7.2-0.20241211102706-b3c5b40b7ceb 11 Dec 2024 none Apache-2.0 — Details →
v1.7.2-0.20241125101459-248eb0f1fb85 25 Nov 2024 none Apache-2.0 — Details →
v1.7.2-0.20241121103001-6dd57e379f39 21 Nov 2024 none Apache-2.0 — Details →
v1.7.2-0.20241120095005-dbf2dc51b5d8 20 Nov 2024 none Apache-2.0 — Details →
v1.7.2-0.20241118103546-3c7eae22d34f 18 Nov 2024 none Apache-2.0 — Details →
v1.7.2-0.20241111163958-94ef9a82fffe 11 Nov 2024 none Apache-2.0 — Details →
v1.7.2-0.20241108092640-6bbbd5f23b6f 08 Nov 2024 none Apache-2.0 — Details →
v1.7.2-0.20241014093103-17245e6dda24 14 Oct 2024 none Apache-2.0 — Details →
v1.7.2-0.20241007121617-05c339acf58e 07 Oct 2024 none Apache-2.0 — Details →
v1.7.2-0.20241007095146-e85745ca6578 07 Oct 2024 none Apache-2.0 — Details →
v1.7.2-0.20241002090420-fb3d01ed0133 02 Oct 2024 none Apache-2.0 — Details →
v1.7.2-0.20241002074941-2378878d97ec 02 Oct 2024 none Apache-2.0 — Details →
v1.7.2-0.20241001174701-12885e5e5f22 01 Oct 2024 none Apache-2.0 — Details →
v1.7.2-0.20240821012221-919aa896f7d4 21 Aug 2024 none Apache-2.0 — Details →
v1.7.2-0.20240715094231-6864eba14969 15 Jul 2024 none Apache-2.0 — Details →
v1.7.2-0.20240708105852-20973471827a 08 Jul 2024 none Apache-2.0 — Details →
v1.7.2-0.20240705093746-04510c1ffd96 05 Jul 2024 none Apache-2.0 — Details →
v1.7.2-0.20240521104202-b2e7058cd438 21 May 2024 none Apache-2.0 — Details →
v1.7.2-0.20240520100840-35e6cae891ea 20 May 2024 none Apache-2.0 — Details →
v1.7.2-0.20240514131138-51226d3f5b78 14 May 2024 none Apache-2.0 — Details →
v1.7.2-0.20240314073626-2855f7d64cc6 14 Mar 2024 none Apache-2.0 — Details →
v1.7.2-0.20240305111125-e2978bc8ac12 05 Mar 2024 none Apache-2.0 — Details →
v1.7.2-0.20240215120304-64ec50755c1d 15 Feb 2024 none Apache-2.0 — Details →
v1.7.2-0.20240119133506-81ee54b6e729 19 Jan 2024 none Apache-2.0 — Details →
v1.7.2-0.20240111120521-45ad41dbb7e7 11 Jan 2024 none Apache-2.0 — Details →
v1.7.2-0.20231018063215-29d2ab3a5d6c 18 Oct 2023 none Apache-2.0 — Details →
v1.7.1 18 Oct 2023 none Apache-2.0 — Details →
v1.7.0 18 Oct 2023 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/kubepug/kubepug

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

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

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

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

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

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

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

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

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