Vulnerability Database · Go · Package report
github.com/cilium/fake: vulnerability history, versions and safety
github.com/cilium/fake 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 github.com/cilium/fake v0.7.0 i
Updated on 23 Oct 2026
Good news: v0.7.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Little adoption
- Community Quiet
What to do: Stay on v0.7.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.7.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.7.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 28 i
- OpenSSF scorecard 4/10 i
- Last release 20 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/cilium/fake, 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.7.1-0.20260903095415-13fc014c1623 03 Sep 2026
- v0.7.1-0.20250915124742-5431f7242da8 15 Sep 2025
- v0.7.1-0.20250910125151-006e3ec4e9e3 10 Sep 2025
- v0.7.0 28 Jan 2025
- v0.7.1-0.20250128100430-4458f87fd7e1 28 Jan 2025
- v0.6.2-0.20241205133741-725cc246c00a 05 Dec 2024
- v0.6.2-0.20241125090216-f3df99df2b9f 25 Nov 2024
- v0.6.2-0.20241115081638-f3b803c7691c 15 Nov 2024
- v0.6.2-0.20241111080316-6c883d3161ca 11 Nov 2024
- v0.6.2-0.20240906125905-3e2c362808d5 06 Sep 2024
- v0.6.2-0.20240807083815-b28a3b67c4cc 07 Aug 2024
- v0.6.2-0.20240708102150-c88aa426ca52 08 Jul 2024
- v0.6.2-0.20240613071645-966c3eecd6c4 13 Jun 2024
- v0.6.2-0.20240517074823-9bcd7ec230fd 17 May 2024
- v0.6.2-0.20240313123957-043d1ba2ea19 13 Mar 2024
- v0.6.2-0.20240212111131-5b04b82d1dfa 12 Feb 2024
- v0.6.2-0.20240124130803-b270feade2ee 24 Jan 2024
- v0.6.2-0.20240109141242-b58f089c770d 09 Jan 2024
- v0.6.1 20 Dec 2023
- v0.6.2-0.20231220110158-8a6877eae70d 20 Dec 2023
- v0.6.1-0.20231219164939-b6249dc0373c 19 Dec 2023
- v0.6.1-0.20231219142641-2f340498b793 19 Dec 2023
- v0.6.0 18 Dec 2023
- v0.6.1-0.20231218160714-6c738dd9e612 18 Dec 2023
- v0.5.1-0.20230809082707-deb9e782718c 09 Aug 2023
- v0.5.0 20 Jul 2023
- v0.5.1-0.20230720090131-2dcc6bbfdcea 20 Jul 2023
- v0.4.0 26 Apr 2023
- v0.4.1-0.20230426142605-6987bf15c3c4 26 Apr 2023
- v0.3.1-0.20230106092002-7292b39c1a26 06 Jan 2023
- v0.3.0 07 Oct 2022
- v0.3.1-0.20221007183627-3d3013e44d9b 07 Oct 2022
- v0.1.1-0.20220915105400-d8607ef8c76a 15 Sep 2022
- v0.2.0 14 Sep 2022
- v0.1.0 18 Aug 2022
- v0.1.1-0.20220818124826-0fe76c8485da 18 Aug 2022
- v0.0.0-20220817154532-089b0adc7d9d 17 Aug 2022
- v0.0.0-20220610094544-a6d440143124 10 Jun 2022
- v0.0.0-20220125155518-c3f8df137cb9 25 Jan 2022
- v0.0.0-20220121140957-c3e2e930fc0d 21 Jan 2022
- v0.0.0-20220121102057-515ccadeac88 21 Jan 2022
- v0.0.0-20220120143951-3faf67ae2071 20 Jan 2022
All 42 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/cilium/fake
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 github.com/cilium/fake
Is github.com/cilium/fake safe to use?
Vulert has no vulnerabilities on record for github.com/cilium/fake 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/cilium/fake's Vulert package health score?
Vulert scores github.com/cilium/fake 60/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/cilium/fake affected?
No. v0.7.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/cilium/fake should I use?
v0.7.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/cilium/fake have?
0 vulnerabilities are recorded for github.com/cilium/fake 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/cilium/fake vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/cilium/fake 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/cilium/fake 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/cilium/fake for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/cilium/fake version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.