VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/kubescape/k8s-interface: vulnerability history, versions and safety

github.com/kubescape/k8s-interface 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/kubescape/k8s-interface vulnerabilities

Vulert verdict on github.com/kubescape/k8s-interface v0.0.230 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v0.0.230 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 6 i
  • Last release this month 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/kubescape/k8s-interface, 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.230 09 Oct 2026 none Apache-2.0 — Details →
v0.0.229 05 Oct 2026 none Apache-2.0 — Details →
v0.0.228 01 Oct 2026 none Apache-2.0 — Details →
v0.0.227 30 Sep 2026 none Apache-2.0 — Details →
v0.0.226 29 Sep 2026 none Apache-2.0 — Details →
v0.0.225 28 Sep 2026 none Apache-2.0 — Details →
v0.0.224 23 Sep 2026 none Apache-2.0 — Details →
v0.0.223 22 Sep 2026 none Apache-2.0 — Details →
v0.0.222 22 Sep 2026 none Apache-2.0 — Details →
v0.0.221 09 Sep 2026 none Apache-2.0 — Details →
v0.0.220 01 Sep 2026 none Apache-2.0 — Details →
v0.0.219 01 Sep 2026 none Apache-2.0 — Details →
v0.0.218 17 Aug 2026 none Apache-2.0 — Details →
v0.0.218-0.20260815050130-fa6fe1e9bc98 15 Aug 2026 none Apache-2.0 — Details →
v0.0.217 08 Aug 2026 none Apache-2.0 — Details →
v0.0.216 03 Aug 2026 none Apache-2.0 — Details →
v0.0.215 31 Jul 2026 none Apache-2.0 — Details →
v0.0.214 03 Jun 2026 none Apache-2.0 — Details →
v0.0.213 21 May 2026 none Apache-2.0 — Details →
v0.0.212 21 May 2026 none Apache-2.0 — Details →
v0.0.211 19 May 2026 none Apache-2.0 — Details →
v0.0.210 18 May 2026 none Apache-2.0 — Details →
v0.0.209 06 May 2026 none Apache-2.0 — Details →
v0.0.208 29 Apr 2026 none Apache-2.0 — Details →
v0.0.207 27 Apr 2026 none Apache-2.0 — Details →
v0.0.207-0.20260427091243-e47bc1304bb4 27 Apr 2026 none Apache-2.0 — Details →
v0.0.206 19 Mar 2026 none Apache-2.0 — Details →
v0.0.206-0.20260319150457-87bba79f7cda 19 Mar 2026 none Apache-2.0 — Details →
v0.0.205 13 Mar 2026 none Apache-2.0 — Details →
v0.0.205-0.20260313104241-022018514b99 13 Mar 2026 none Apache-2.0 — Details →
v0.0.204 09 Mar 2026 none Apache-2.0 — Details →
v0.0.204-0.20260308171143-7970175a8df6 08 Mar 2026 none Apache-2.0 — Details →
v0.0.203 11 Feb 2026 none Apache-2.0 — Details →
v0.0.202 21 Jan 2026 none Apache-2.0 — Details →
v0.0.201 19 Jan 2026 none Apache-2.0 — Details →
v0.0.201-0.20260119170408-4c38f5a77c0f 19 Jan 2026 none Apache-2.0 — Details →
v0.0.201-0.20251006104302-0a264e0bed27 06 Oct 2025 none Apache-2.0 — Details →
v0.0.200 30 Sep 2025 none Apache-2.0 — Details →
v0.0.199 05 Sep 2025 none Apache-2.0 — Details →
v0.0.199-0.20250905052438-06da6832fdf6 05 Sep 2025 none Apache-2.0 — Details →
v0.0.199-0.20250811101530-f0f93bc9cf8a 11 Aug 2025 none Apache-2.0 — Details →
v0.0.198 29 Jul 2025 none Apache-2.0 — Details →
v0.0.198-0.20250729113335-e06ca8345b9b 29 Jul 2025 none Apache-2.0 — Details →
v0.0.197 01 Jul 2025 none Apache-2.0 — Details →
v0.0.196 30 Jun 2025 none Apache-2.0 — Details →
v0.0.196-0.20250629105546-2a317a6686fe 29 Jun 2025 none Apache-2.0 — Details →
v0.0.196-0.20250605131454-ebc0f2a0390c 05 Jun 2025 none Apache-2.0 — Details →
v0.0.196-0.20250605115847-ac24779614eb 05 Jun 2025 none Apache-2.0 — Details →
v0.0.196-0.20250602081120-58b554deea54 02 Jun 2025 none Apache-2.0 — Details →
v0.0.196-0.20250602064013-c41d5defbdfd 02 Jun 2025 none Apache-2.0 — Details →
v0.0.196-0.20250529061927-10afa14287f5 29 May 2025 none Apache-2.0 — Details →
v0.0.195-0.20250527060553-80251dee6213 27 May 2025 none Apache-2.0 — Details →
v0.0.195-0.20250526161232-0c2fe66112c2 26 May 2025 none Apache-2.0 — Details →
v0.0.195 07 May 2025 none Apache-2.0 — Details →
v0.0.195-0.20250507123551-8f651ac53ae6 07 May 2025 none Apache-2.0 — Details →
v0.0.194 06 May 2025 none Apache-2.0 — Details →
v0.0.193 01 May 2025 none Apache-2.0 — Details →
v0.0.193-0.20250501061427-965b41611b24 01 May 2025 none Apache-2.0 — Details →
v0.0.192 23 Apr 2025 none Apache-2.0 — Details →
v0.0.192-0.20250423111014-ea50590430f7 23 Apr 2025 none Apache-2.0 — Details →
v0.0.192-0.20250422112419-6cd335894140 22 Apr 2025 none Apache-2.0 — Details →
v0.0.192-0.20250417145740-56f724750595 17 Apr 2025 none Apache-2.0 — Details →
v0.0.191 14 Apr 2025 none Apache-2.0 — Details →
v0.0.191-0.20250414131555-0177b5c7e298 14 Apr 2025 none Apache-2.0 — Details →
v0.0.190 27 Feb 2025 none Apache-2.0 — Details →
v0.0.189 18 Feb 2025 none Apache-2.0 — Details →
v0.0.189-0.20250217154244-190cc71ef91f 17 Feb 2025 none Apache-2.0 — Details →
v0.0.188 11 Feb 2025 none Apache-2.0 — Details →
v0.0.187 10 Feb 2025 none Apache-2.0 — Details →
v0.0.186 07 Feb 2025 none Apache-2.0 — Details →
v0.0.185 04 Feb 2025 none Apache-2.0 — Details →
v0.0.184 04 Feb 2025 none Apache-2.0 — Details →
v0.0.184-0.20250204123652-45ab50c665d8 04 Feb 2025 none Apache-2.0 — Details →
v0.0.183 30 Jan 2025 none Apache-2.0 — Details →
v0.0.182 29 Jan 2025 none Apache-2.0 — Details →
v0.0.182-0.20250129173721-b45899af5d6d 29 Jan 2025 none Apache-2.0 — Details →
v0.0.181 17 Jan 2025 none Apache-2.0 — Details →
v0.0.180 16 Jan 2025 none Apache-2.0 — Details →
v0.0.179 15 Dec 2024 none Apache-2.0 — Details →
v0.0.178 12 Dec 2024 none Apache-2.0 — Details →
v0.0.178-0.20241210133841-deb34e2a28b5 10 Dec 2024 none Apache-2.0 — Details →
v0.0.178-0.20241126104134-36ecfb439c3e 26 Nov 2024 none Apache-2.0 — Details →
v0.0.177 15 Nov 2024 none Apache-2.0 — Details →
v0.0.177-0.20241115131737-2dc89b701338 15 Nov 2024 none Apache-2.0 — Details →
v0.0.176 26 Sep 2024 none Apache-2.0 — Details →
v0.0.175-0.20240926103743-f9087cb77121 26 Sep 2024 none Apache-2.0 — Details →
v0.0.175 26 Sep 2024 none Apache-2.0 — Details →
v0.0.175-0.20240926095353-4aef3f6fdeda 26 Sep 2024 none Apache-2.0 — Details →
v0.0.174 23 Sep 2024 none Apache-2.0 — Details →
v0.0.173 19 Sep 2024 none Apache-2.0 — Details →
v0.0.172 09 Sep 2024 none Apache-2.0 — Details →
v0.0.171 29 Aug 2024 none Apache-2.0 — Details →
v0.0.170 19 Jul 2024 none Apache-2.0 — Details →
v0.0.170-0.20240718151504-0761af7c089c 18 Jul 2024 none Apache-2.0 — Details →
v0.0.170-0.20240717114221-8a3071c26892 17 Jul 2024 none Apache-2.0 — Details →
v0.0.170-0.20240717074243-384ee2aeb91f 17 Jul 2024 none Apache-2.0 — Details →
v0.0.170-0.20240715053520-a8d00bd02388 15 Jul 2024 none Apache-2.0 — Details →
v0.0.169 09 Jun 2024 none Apache-2.0 — Details →
v0.0.168 26 May 2024 none Apache-2.0 — Details →
v0.0.168-0.20240526121959-2c77cfcf2717 26 May 2024 none Apache-2.0 — Details →
v0.0.167 26 May 2024 none — — Details →
v0.0.166 05 May 2024 none — — Details →
v0.0.165 05 Apr 2024 none — — Details →
v0.0.165-0.20240404093458-3aea7e70c96f 04 Apr 2024 none — — Details →
v0.0.164 04 Apr 2024 none — — Details →
v0.0.164-0.20240318184904-556252aa99e3 18 Mar 2024 none — — Details →
v0.0.163 11 Mar 2024 none — — Details →
v0.0.162 07 Mar 2024 none — — Details →
v0.0.162-0.20240307132104-81bb25de033f 07 Mar 2024 none — — Details →
v0.0.162-0.20240307130714-f02ecbd701e5 07 Mar 2024 none — — Details →
v0.0.161 26 Feb 2024 none — — Details →
v0.0.160 22 Feb 2024 none — — Details →
v0.0.159 19 Feb 2024 none — — Details →
v0.0.159-0.20240128085543-a829d861c684 28 Jan 2024 none — — Details →
v0.0.158 24 Jan 2024 none — — Details →
v0.0.158-0.20240123155300-c2a152fdc0d8 23 Jan 2024 none — — Details →
v0.0.158-0.20240117162237-b087cd69bcf1 17 Jan 2024 none — — Details →
v0.0.158-0.20240117153244-6145fd243723 17 Jan 2024 none — — Details →
v0.0.157 11 Jan 2024 none — — Details →
v0.0.157-0.20240111111316-e6d8909fade9 11 Jan 2024 none — — Details →

The newest 120 of 212 versions Vulert tracks. 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/kubescape/k8s-interface

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/kubescape/k8s-interface

Is github.com/kubescape/k8s-interface safe to use?

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

Vulert scores github.com/kubescape/k8s-interface 77/100, which reads as in good shape. 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/kubescape/k8s-interface affected?

No. v0.0.230, 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/kubescape/k8s-interface should I use?

v0.0.230 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/kubescape/k8s-interface have?

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

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

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