Vulnerability Database · Go · Package report
sigs.k8s.io/mcs-api/controllers: vulnerability history, versions and safety
sigs.k8s.io/mcs-api/controllers is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on sigs.k8s.io/mcs-api/controllers v0.5.2 i
Updated on 23 Oct 2026
Good news: v0.5.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v0.5.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.5.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.5.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 261 i
- OpenSSF scorecard 5/10 i
- Last release 3 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 sigs.k8s.io/mcs-api/controllers, 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.
- v0.5.2 13 Jul 2026
- v0.5.1-0.20260706124828-93680909f9e5 06 Jul 2026
- v0.5.1-0.20260611073251-db147c3e167e 11 Jun 2026
- v0.5.0 05 May 2026
- v0.4.1 29 Apr 2026
- v0.0.0-20260429083924-5705abe7792b 29 Apr 2026
- v0.0.0-20260415161103-2525ee33f2a4 15 Apr 2026
- v0.0.0-20260409075333-1a2379166c5e 09 Apr 2026
- v0.0.0-20260407164133-5bcc85f3b4a5 07 Apr 2026
- v0.0.0-20260403094305-4b9911b73f14 03 Apr 2026
- v0.0.0-20260402102705-0a064be761a2 02 Apr 2026
- v0.0.0-20260311160536-15301c2b6a81 11 Mar 2026
- v0.0.0-20260303164920-6a4a49e0c6d1 03 Mar 2026
- v0.0.0-20260224125735-0f775a3eff97 24 Feb 2026
- v0.0.0-20260211180202-33f6d88209e1 11 Feb 2026
- v0.0.0-20260211162400-9e5f5eedd10e 11 Feb 2026
- v0.0.0-20260211161402-2dfedbd26971 11 Feb 2026
- v0.0.0-20251224112231-f4767b9e5a04 24 Dec 2025
- v0.0.0-20251217171610-79faa199f7dd 17 Dec 2025
- v0.0.0-20251209180531-e481ae73a51f 09 Dec 2025
- v0.0.0-20251016174042-a93ef0180a10 16 Oct 2025
- v0.0.0-20251009195101-44eb57759015 09 Oct 2025
- v0.0.0-20250911135410-b2223d716ee2 11 Sep 2025
- v0.0.0-20250911133809-32a9209a5972 11 Sep 2025
- v0.0.0-20250910114959-da2c058931fc 10 Sep 2025
- v0.0.0-20250908143931-c8d01f8691dc 08 Sep 2025
- v0.0.0-20250908090929-79efdd37ed2b 08 Sep 2025
- v0.0.0-20250904084517-2bb7deef8524 04 Sep 2025
- v0.0.0-20250901132913-8da32eba50d6 01 Sep 2025
- v0.0.0-20250829140448-1abb72e95b30 29 Aug 2025
- v0.0.0-20250829140111-398bcaa1425c 29 Aug 2025
- v0.0.0-20250829115709-85bcb03e18e8 29 Aug 2025
- v0.0.0-20250829115509-f6fc7ddd0679 29 Aug 2025
- v0.0.0-20250826145214-0d87c31a767d 26 Aug 2025
- v0.0.0-20250825122509-a519a188f757 25 Aug 2025
- v0.0.0-20250731081715-a807ec696257 31 Jul 2025
- v0.0.0-20250724073829-5b846203867b 24 Jul 2025
- v0.0.0-20250715173623-20de0ebd811c 15 Jul 2025
- v0.0.0-20250619142051-a23ff80a0902 19 Jun 2025
- v0.0.0-20250610011024-38bab5ba476b 10 Jun 2025
- v0.0.0-20250609120224-89a35689fec7 09 Jun 2025
- v0.0.0-20250513123917-5e5359a979c7 13 May 2025
- v0.0.0-20250224121229-6c631f4730d0 24 Feb 2025
- v0.0.0-20250129110323-a7986579439f 29 Jan 2025
- v0.0.0-20250127122723-efcb2f8996f0 27 Jan 2025
All 45 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 sigs.k8s.io/mcs-api/controllers
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
Questions
About sigs.k8s.io/mcs-api/controllers
Is sigs.k8s.io/mcs-api/controllers safe to use?
Vulert has no vulnerabilities on record for sigs.k8s.io/mcs-api/controllers 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 sigs.k8s.io/mcs-api/controllers's Vulert package health score?
Vulert scores sigs.k8s.io/mcs-api/controllers 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 sigs.k8s.io/mcs-api/controllers affected?
No. v0.5.2, 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 sigs.k8s.io/mcs-api/controllers should I use?
v0.5.2 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 sigs.k8s.io/mcs-api/controllers have?
0 vulnerabilities are recorded for sigs.k8s.io/mcs-api/controllers 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 sigs.k8s.io/mcs-api/controllers vulnerabilities disclosed?
0 vulnerabilities were recorded for sigs.k8s.io/mcs-api/controllers 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 sigs.k8s.io/mcs-api/controllers 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 sigs.k8s.io/mcs-api/controllers for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the sigs.k8s.io/mcs-api/controllers version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.