VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/rancher/wharfie: vulnerability history, versions and safety

github.com/rancher/wharfie 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/rancher/wharfie vulnerabilities

Vulert verdict on github.com/rancher/wharfie v0.7.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release v0.7.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 38 i
  • OpenSSF scorecard 5/10 i
  • Last release 7 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/rancher/wharfie, 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.8.0-rc2 11 Jun 2026 none Apache-2.0 — Details →
v0.8.0-rc1 10 Jun 2026 none Apache-2.0 — Details →
v0.7.1 06 Mar 2026 none Apache-2.0 — Details →
v0.7.1-0.20251014190711-8cfe84a9efaa 14 Oct 2025 none Apache-2.0 — Details →
v0.7.0 29 Apr 2025 none Apache-2.0 — Details →
v0.6.9 11 Feb 2025 none Apache-2.0 — Details →
v0.6.9-0.20250211234636-0b732645458a 11 Feb 2025 none Apache-2.0 — Details →
v0.6.8 01 Dec 2024 none Apache-2.0 — Details →
v0.6.8-0.20241201194209-16ec24e09bc3 01 Dec 2024 none Apache-2.0 — Details →
v0.6.8-0.20241106214129-3479c9f36a37 06 Nov 2024 none Apache-2.0 — Details →
v0.6.7 01 Oct 2024 none Apache-2.0 — Details →
v0.6.7-0.20241001223324-f0590c66dd86 01 Oct 2024 none Apache-2.0 — Details →
v0.6.7-0.20241001203142-066c9c3e27f1 01 Oct 2024 none Apache-2.0 — Details →
v0.6.7-0.20240621224626-08b66f5b2376 21 Jun 2024 none Apache-2.0 — Details →
v0.6.6 23 Feb 2024 none Apache-2.0 — Details →
v0.6.6-0.20240223202316-df922ffcf473 23 Feb 2024 none Apache-2.0 — Details →
v0.6.5 16 Jan 2024 none Apache-2.0 — Details →
v0.6.5-0.20240116183436-d6940bee18f6 16 Jan 2024 none Apache-2.0 — Details →
v0.6.4 08 Dec 2023 none Apache-2.0 — Details →
v0.6.4-0.20231208215711-afa72eb3bb2e 08 Dec 2023 none Apache-2.0 — Details →
v0.6.3 30 Oct 2023 none Apache-2.0 — Details →
v0.6.3-0.20231030181832-5a9199d78319 30 Oct 2023 none Apache-2.0 — Details →
v0.6.2 06 Jun 2023 none Apache-2.0 — Details →
v0.6.2-0.20230606233804-cf9a8880fbd7 06 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230307005740-9ed85f608166 07 Mar 2023 none Apache-2.0 — Details →
v0.6.1 10 Jan 2023 none Apache-2.0 — Details →
v0.6.0 23 Dec 2022 none Apache-2.0 — Details →
v0.6.0-rc.0.0.20221223183231-c1c008f82004 23 Dec 2022 none Apache-2.0 — Details →
v0.6.0-rc.1 23 Dec 2022 none Apache-2.0 — Details →
v0.5.4-0.20221223021707-3b4580339236 23 Dec 2022 none Apache-2.0 — Details →
v0.6.0-rc.0 23 Dec 2022 none Apache-2.0 — Details →
v0.5.3 13 Apr 2022 none Apache-2.0 — Details →
v0.5.2 22 Dec 2021 none Apache-2.0 — Details →
v0.5.1 01 Dec 2021 none Apache-2.0 — Details →
v0.4.4-0.20211116101616-5cc85f23e668 16 Nov 2021 none Apache-2.0 — Details →
v0.5.0 16 Nov 2021 none Apache-2.0 — Details →
v0.4.4-0.20211104211917-c8666a42d8b1 04 Nov 2021 none Apache-2.0 — Details →
v0.4.3 03 Nov 2021 none Apache-2.0 — Details →
v0.4.2 31 Aug 2021 none Apache-2.0 — Details →
v0.4.1 08 Jul 2021 none Apache-2.0 — Details →
v0.4.0 09 Jun 2021 none Apache-2.0 — Details →
v0.3.5 12 May 2021 none Apache-2.0 — Details →
v0.3.4 07 May 2021 none Apache-2.0 — Details →
v0.3.3 06 May 2021 none Apache-2.0 — Details →
v0.3.2 04 May 2021 none Apache-2.0 — Details →
v0.3.1 04 May 2021 none Apache-2.0 — Details →
v0.3.1-0.20210504004606-9782396fcb96 04 May 2021 none Apache-2.0 — Details →
v0.3.0 04 May 2021 none Apache-2.0 — Details →
v0.2.0 03 May 2021 none Apache-2.0 — Details →
v0.1.1-0.20210503113938-e1fd2f6b6a81 03 May 2021 none Apache-2.0 — Details →
v0.1.0 03 May 2021 none Apache-2.0 — Details →

All 51 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/rancher/wharfie

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/rancher/wharfie

Is github.com/rancher/wharfie safe to use?

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

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

No. v0.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/rancher/wharfie should I use?

v0.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/rancher/wharfie have?

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

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

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