Vulnerability Database · Go · Package report
github.com/allegro/bigcache: vulnerability history, versions and safety
github.com/allegro/bigcache 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/allegro/bigcache v1.2.1 i
Updated on 23 Oct 2026
Good news: v1.2.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Key ecosystem project
- Community Moderate
What to do: Stay on v1.2.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.2.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 8,173 i
- OpenSSF scorecard 4/10 i
- Last release 88 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/allegro/bigcache, 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.0.0-20190618191010-69ea0af04088 18 Jun 2019
- v1.2.2-0.20190618191010-69ea0af04088 18 Jun 2019
- v1.2.1 18 Jun 2019
- v0.0.0-20190218064605-e24eb225f156 18 Feb 2019
- v1.1.1-0.20190218064605-e24eb225f156 18 Feb 2019
- v1.2.1-0.20190218064605-e24eb225f156 18 Feb 2019
- v0.0.0-20190116153254-84a0ff3f153c 16 Jan 2019
- v1.1.1-0.20190116153254-84a0ff3f153c 16 Jan 2019
- v1.2.0 16 Jan 2019
- v0.0.0-20190111124714-159fb018d398 11 Jan 2019
- v1.1.1-0.20190111124714-159fb018d398 11 Jan 2019
- v0.0.0-20181125133012-06975fd8de98 25 Nov 2018
- v1.1.1-0.20181125133012-06975fd8de98 25 Nov 2018
- v0.0.0-20181022200625-bff00e20c68d 22 Oct 2018
- v1.1.1-0.20181022200625-bff00e20c68d 22 Oct 2018
- v0.0.0-20181021151058-4888ee399352 21 Oct 2018
- v1.1.1-0.20181021151058-4888ee399352 21 Oct 2018
- v0.0.0-20181009050124-70fdb6c1fbb8 09 Oct 2018
- v1.1.1-0.20181009050124-70fdb6c1fbb8 09 Oct 2018
- v0.0.0-20180910063704-5946793e3c8e 10 Sep 2018
- v1.1.1-0.20180910063704-5946793e3c8e 10 Sep 2018
- v1.1.1-0.20180831062217-5e5c707aa724 31 Aug 2018
- v0.0.0-20180827093018-05ff80d090fd 27 Aug 2018
- v1.1.1-0.20180827093018-05ff80d090fd 27 Aug 2018
- v0.0.0-20180423221942-ca9a59ef2ad9 23 Apr 2018
- v1.1.1-0.20180423221942-ca9a59ef2ad9 23 Apr 2018
- v0.0.0-20180423150211-738572604712 23 Apr 2018
- v1.1.1-0.20180423150211-738572604712 23 Apr 2018
- v0.0.0-20180329152823-e3e2429e52c3 29 Mar 2018
- v1.1.1-0.20180329152823-e3e2429e52c3 29 Mar 2018
- v0.0.0-20180327112218-f31987a23e44 27 Mar 2018
- v1.1.0 27 Mar 2018
- v1.0.1-0.20180324123721-05108113b7a5 24 Mar 2018
- v0.0.0-20171130114223-62db14428113 30 Nov 2017
- v1.0.1-0.20171130114223-62db14428113 30 Nov 2017
- v1.0.1-0.20171128211905-d5e625d6d1a8 28 Nov 2017
- v0.0.0-20171115103432-53bd79e3bbd9 15 Nov 2017
- v1.0.1-0.20171115103432-53bd79e3bbd9 15 Nov 2017
- v1.0.1-0.20171029182044-90fa9833b8b9 29 Oct 2017
- v1.0.1-0.20171012163946-3e33de51947d 12 Oct 2017
- v1.0.1-0.20171010084156-7ffd75d9082f 10 Oct 2017
- v0.0.0-20170925151751-7487d18e1f91 25 Sep 2017
- v1.0.1-0.20170925151751-7487d18e1f91 25 Sep 2017
- v1.0.0 20 Sep 2017
- v0.0.0-20170908180301-62de4dac703d 08 Sep 2017
- v0.0.0-20170828111853-95bb0d0348a4 28 Aug 2017
- v0.0.0-20170807115914-77a4c85c42e9 07 Aug 2017
- v0.0.0-20170807104739-24eb6cbe47dd 07 Aug 2017
- v0.0.0-20170418084644-b6bd76ad0f79 18 Apr 2017
- v0.0.0-20170227101859-dedad99b9443 27 Feb 2017
- v0.0.0-20170217111307-c67c16c667c0 17 Feb 2017
- v0.0.0-20161104090447-d542a6d8996a 04 Nov 2016
- v0.0.0-20161103095534-83187d7531f1 03 Nov 2016
- v0.0.0-20161102220630-216b1fe874f2 02 Nov 2016
- v0.0.0-20161019150228-183ce8df9d1d 19 Oct 2016
- v0.0.0-20161012175207-5b5116bbfd40 12 Oct 2016
- v0.0.0-20161012145911-f403062367f6 12 Oct 2016
- v0.0.0-20160828113001-90098c54320d 28 Aug 2016
- v0.0.0-20160607113427-966b0b478980 07 Jun 2016
- v0.0.0-20160606095901-69eeed682321 06 Jun 2016
- v0.0.0-20160506113159-6854b9e777a0 06 May 2016
- v0.0.0-20160422073523-662723b6a7d4 22 Apr 2016
- v0.0.0-20160330083222-1ed87ff80c63 30 Mar 2016
All 63 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/allegro/bigcache
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/allegro/bigcache
Is github.com/allegro/bigcache safe to use?
Vulert has no vulnerabilities on record for github.com/allegro/bigcache 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/allegro/bigcache's Vulert package health score?
Vulert scores github.com/allegro/bigcache 65/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/allegro/bigcache affected?
No. v1.2.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/allegro/bigcache should I use?
v1.2.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/allegro/bigcache have?
0 vulnerabilities are recorded for github.com/allegro/bigcache 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/allegro/bigcache vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/allegro/bigcache 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/allegro/bigcache 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/allegro/bigcache for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/allegro/bigcache version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.