Vulnerability Database · Go · Package report
github.com/blugelabs/ice: vulnerability history, versions and safety
github.com/blugelabs/ice 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/blugelabs/ice v1.0.0 i
Updated on 23 Oct 2026
Good news: v1.0.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 12 i
- OpenSSF scorecard 2/10 i
- Last release 52 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/blugelabs/ice, 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.
- v1.0.1-0.20220526124209-80ce9b5e8454 26 May 2022
- v1.0.1-0.20220526123516-8b0e8c2cad4a 26 May 2022
- v1.0.0 26 May 2022
- v0.2.1-0.20220524230234-111b14df08fb 24 May 2022
- v0.2.0 13 Jul 2021
- v0.1.2-0.20200929235126-5256fecadef4 29 Sep 2020
- v0.1.2-0.20200929232102-54fa7d308d21 29 Sep 2020
- v0.1.2-0.20200929134837-703dfcaa749f 29 Sep 2020
- v0.1.2-0.20200929134644-36c01ba9f512 29 Sep 2020
- v0.1.2-0.20200929133941-91afc9de8c7e 29 Sep 2020
- v0.1.2-0.20200929133706-548f95ce0286 29 Sep 2020
- v0.1.2-0.20200929130943-5d0f326181b0 29 Sep 2020
- v0.1.1 29 Sep 2020
- v0.1.1-0.20200929123819-cdec34413467 29 Sep 2020
- v0.1.0 28 Sep 2020
- v0.0.0-20200927225502-ea4843c9f22e 27 Sep 2020
- v0.0.0-20200903182823-89f4358cbab0 03 Sep 2020
- v0.0.0-20200902173709-5fd33245d802 02 Sep 2020
- v0.0.0-20200902173449-2bd928572c8d 02 Sep 2020
- v0.0.0-20200830021339-36efd2395bc6 30 Aug 2020
- v0.0.0-20200830021325-883a1123a797 30 Aug 2020
- v0.0.0-20200830021252-d05808bbdcd6 30 Aug 2020
- v0.0.0-20200812141057-816bad8c15e7 12 Aug 2020
- v0.0.0-20200812140951-445b1a316045 12 Aug 2020
- v0.0.0-20200812133313-f59b267a0c8a 12 Aug 2020
- v0.0.0-20200812025759-c8449ad6c63e 12 Aug 2020
All 26 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/blugelabs/ice
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/blugelabs/ice
Is github.com/blugelabs/ice safe to use?
Vulert has no vulnerabilities on record for github.com/blugelabs/ice 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/blugelabs/ice's Vulert package health score?
Vulert scores github.com/blugelabs/ice 44/100, which reads as risky. 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/blugelabs/ice affected?
No. v1.0.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/blugelabs/ice should I use?
v1.0.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/blugelabs/ice have?
0 vulnerabilities are recorded for github.com/blugelabs/ice 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/blugelabs/ice vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/blugelabs/ice 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/blugelabs/ice 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/blugelabs/ice for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/blugelabs/ice version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.