VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/openkruise/kruise-api: vulnerability history, versions and safety

github.com/openkruise/kruise-api 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/openkruise/kruise-api vulnerabilities

Vulert verdict on github.com/openkruise/kruise-api v1.8.0 i

Updated on 23 Oct 2026

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

Package health score 58/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v1.8.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 30 i
  • OpenSSF scorecard 2/10 i
  • Last release 18 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/openkruise/kruise-api, 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-20251226151007-f5f0da530ad5 26 Dec 2025 none Apache-2.0 — Details →
v1.8.1-0.20251226151007-f5f0da530ad5 26 Dec 2025 none Apache-2.0 — Details →
v1.8.0 02 Apr 2025 none Apache-2.0 — Details →
v1.7.2-0.20250218113446-8f1a2ead57a4 18 Feb 2025 none Apache-2.0 — Details →
v1.7.1 26 Sep 2024 none Apache-2.0 — Details →
v1.7.1-0.20240926071401-aa204718cc4d 26 Sep 2024 none Apache-2.0 — Details →
v1.6.1-0.20240904030658-7e4db51c55b4 04 Sep 2024 none Apache-2.0 — Details →
v1.7.0 04 Sep 2024 none Apache-2.0 — Details →
v1.5.1-0.20240322060526-bc7731fc53af 22 Mar 2024 none Apache-2.0 — Details →
v1.6.0 22 Mar 2024 none Apache-2.0 — Details →
v1.5.1-0.20240131014039-3aaf0eafa4ed 31 Jan 2024 none Apache-2.0 — Details →
v1.4.1-0.20231016083138-fb3acc0764ed 16 Oct 2023 none Apache-2.0 — Details →
v1.5.0 16 Oct 2023 none Apache-2.0 — Details →
v1.4.1-0.20230929082623-fba43ee6a7e9 29 Sep 2023 none Apache-2.0 — Details →
v1.3.1-0.20230418040156-dfd85d2d89d0 18 Apr 2023 none Apache-2.0 — Details →
v1.4.0 17 Mar 2023 none Apache-2.0 — Details →
v1.3.1-0.20230220075204-a736eeceb4f7 20 Feb 2023 none Apache-2.0 — Details →
v1.3.1-0.20230217053002-9ac94c7f0ac4 17 Feb 2023 none Apache-2.0 — Details →
v1.3.1-0.20230111022228-0631c9ba996b 11 Jan 2023 none Apache-2.0 — Details →
v1.4.0-rc.0 10 Jan 2023 none Apache-2.0 — Details →
v1.3.0 28 Sep 2022 none Apache-2.0 — Details →
v1.2.1-0.20220830035714-d1805e94da3a 30 Aug 2022 none Apache-2.0 — Details →
v1.2.1-0.20220727111652-1d1061813cfb 27 Jul 2022 none Apache-2.0 — Details →
v1.1.1-0.20220524031908-07ee4e21e038 24 May 2022 none Apache-2.0 — Details →
v1.2.0 24 May 2022 none Apache-2.0 — Details →
v1.2.0-beta.0 24 May 2022 none Apache-2.0 — Details →
v1.1.1-0.20220424073643-7d8f48620c79 24 Apr 2022 none Apache-2.0 — Details →
v1.1.0-legacy 28 Mar 2022 none Apache-2.0 — Details →
v1.1.1-0.20220328112136-71eb767f2a85 28 Mar 2022 none Apache-2.0 — Details →
v1.1.0 28 Mar 2022 none Apache-2.0 — Details →
v1.0.1-tmp 09 Feb 2022 none Apache-2.0 — Details →
v1.0.2-0.20220209075707-29604942b4b6 09 Feb 2022 none Apache-2.0 — Details →
v1.0.1 09 Feb 2022 none Apache-2.0 — Details →
v1.0.0 09 Dec 2021 none Apache-2.0 — Details →
v1.0.0-beta.0.0.20211209040245-191320b5e0ce 09 Dec 2021 none Apache-2.0 — Details →
v1.0.0-beta.0-legacy.0.20211207104943-e25fe1bb26ee 07 Dec 2021 none Apache-2.0 — Details →
v1.0.0-legacy 07 Dec 2021 none Apache-2.0 — Details →
v1.0.0-beta.0.0.20211207104748-2acae5a4841e 07 Dec 2021 none Apache-2.0 — Details →
v1.0.0-beta.0-legacy 29 Nov 2021 none Apache-2.0 — Details →
v1.0.0-beta.0.0.20211129093524-047dbb23df79 29 Nov 2021 none Apache-2.0 — Details →
v0.10.1-0.20211129092923-0ce8773a8f25 29 Nov 2021 none Apache-2.0 — Details →
v1.0.0-beta.0 29 Nov 2021 none Apache-2.0 — Details →
v0.10.0-legacy 01 Sep 2021 none Apache-2.0 — Details →
v0.10.1-0.20210901033950-0434da288487 01 Sep 2021 none Apache-2.0 — Details →
v0.10.0 01 Sep 2021 none Apache-2.0 — Details →
v0.9.0-1.18 19 May 2021 none Apache-2.0 — Details →
v0.9.1-0.20210519084944-c0deede5589e 19 May 2021 none Apache-2.0 — Details →
v0.0.0-20210519084330-5f21a3516d6d 19 May 2021 none Apache-2.0 — Details →
v0.9.0 19 May 2021 none Apache-2.0 — Details →
v0.9.0-alpha.0.0.20210421030255-36eee4fc22dd 21 Apr 2021 none Apache-2.0 — Details →
v0.9.0-alpha.1 21 Apr 2021 none Apache-2.0 — Details →
v0.8.1-0.20210413091612-4e4613825256 13 Apr 2021 none Apache-2.0 — Details →
v0.9.0-alpha.0 13 Apr 2021 none Apache-2.0 — Details →
v0.7.1-0.20210304061411-cc22b4b6d6be 04 Mar 2021 none Apache-2.0 — Details →
v0.8.0-1.18 04 Mar 2021 none Apache-2.0 — Details →
v0.8.0 04 Mar 2021 none Apache-2.0 — Details →
v0.7.0-1.18 04 Feb 2021 none Apache-2.0 — Details →
v0.7.1-0.20210204031110-1f6fc9860995 04 Feb 2021 none Apache-2.0 — Details →
v0.7.1-0.20201218022413-a921b921a87a 18 Dec 2020 none Apache-2.0 — Details →
v0.6.2-0.20201215055226-9fee18206366 15 Dec 2020 none Apache-2.0 — Details →
v0.7.0 15 Dec 2020 none Apache-2.0 — Details →
v0.6.2-0.20201209042231-c9745da8bfda 09 Dec 2020 none Apache-2.0 — Details →
v0.6.1 09 Dec 2020 none Apache-2.0 — Details →
v0.6.0 18 Aug 2020 none Apache-2.0 — Details →
v0.5.0 29 May 2020 none Apache-2.0 — Details →
v0.4.1-0.20200326105930-252cba87f9f7 26 Mar 2020 none Apache-2.0 — Details →
v0.4.1-a 26 Mar 2020 none Apache-2.0 — Details →
v0.4.1 24 Mar 2020 none Apache-2.0 — Details →
v0.4.1-pre.1 24 Mar 2020 none Apache-2.0 — Details →
v0.4.0 24 Mar 2020 none Apache-2.0 — Details →

All 70 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/openkruise/kruise-api

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/openkruise/kruise-api

Is github.com/openkruise/kruise-api safe to use?

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

Vulert scores github.com/openkruise/kruise-api 58/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/openkruise/kruise-api affected?

No. v1.8.0, 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/openkruise/kruise-api should I use?

v1.8.0 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/openkruise/kruise-api have?

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

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

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