Vulnerability Database · Go · Package report
github.com/circonus-labs/circonusllhist: vulnerability history, versions and safety
github.com/circonus-labs/circonusllhist 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.
See all github.com/circonus-labs/circonusllhist vulnerabilities
Vulert verdict on github.com/circonus-labs/circonusllhist v0.1.5 i
Updated on 23 Oct 2026
Good news: v0.1.5, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Niche
- Community Inactive
What to do: Stay on v0.1.5 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 93 i
- OpenSSF scorecard 2/10 i
- Last release 68 months ago i
- Licence BSD-3-Clause 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/circonus-labs/circonusllhist, 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.1.6-0.20210223013337-dbd54b03f69f 23 Feb 2021
- v0.1.5 22 Feb 2021
- v0.0.0-20191022123619-ec08cde75a29 22 Oct 2019
- v0.1.4 22 Oct 2019
- v0.1.4-0.20191022123619-ec08cde75a29 22 Oct 2019
- v0.0.0-20181128183103-87d4d00b35ad 28 Nov 2018
- v0.1.3 28 Nov 2018
- v0.1.2 21 Nov 2018
- v0.1.1 20 Nov 2018
- v0.0.0-20180430145027-5eb751da55c6 30 Apr 2018
- v0.1.0 30 Apr 2018
- v0.0.0-20180104205821-1e65893c4458 04 Jan 2018
- v0.0.0-20170525201649-6e85b9352cf0 25 May 2017
- v0.0.0-20161121135153-7d649b46cdc2 21 Nov 2016
- v0.0.0-20161117071941-f558b101b207 17 Nov 2016
- v0.0.0-20161110015105-0e8e86d926b6 10 Nov 2016
- v0.0.0-20161110002650-365d370cc145 10 Nov 2016
- v0.0.0-20160920131806-89791f563a48 20 Sep 2016
- v0.0.0-20160526043813-d724266ae527 26 May 2016
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.1.6-0.20210223013337-dbd54b03f69f | 23 Feb 2021 | none | BSD-3-Clause | — | Details → |
| v0.1.5 | 22 Feb 2021 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20191022123619-ec08cde75a29 | 22 Oct 2019 | none | BSD-3-Clause | — | Details → |
| v0.1.4 | 22 Oct 2019 | none | BSD-3-Clause | — | Details → |
| v0.1.4-0.20191022123619-ec08cde75a29 | 22 Oct 2019 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20181128183103-87d4d00b35ad | 28 Nov 2018 | none | BSD-3-Clause | — | Details → |
| v0.1.3 | 28 Nov 2018 | none | BSD-3-Clause | — | Details → |
| v0.1.2 | 21 Nov 2018 | none | BSD-3-Clause | — | Details → |
| v0.1.1 | 20 Nov 2018 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20180430145027-5eb751da55c6 | 30 Apr 2018 | none | BSD-3-Clause | — | Details → |
| v0.1.0 | 30 Apr 2018 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20180104205821-1e65893c4458 | 04 Jan 2018 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20170525201649-6e85b9352cf0 | 25 May 2017 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20161121135153-7d649b46cdc2 | 21 Nov 2016 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20161117071941-f558b101b207 | 17 Nov 2016 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20161110015105-0e8e86d926b6 | 10 Nov 2016 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20161110002650-365d370cc145 | 10 Nov 2016 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20160920131806-89791f563a48 | 20 Sep 2016 | none | BSD-3-Clause | — | Details → |
| v0.0.0-20160526043813-d724266ae527 | 26 May 2016 | none | BSD-3-Clause | — | Details → |
All 19 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/circonus-labs/circonusllhist
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/circonus-labs/circonusllhist
Is github.com/circonus-labs/circonusllhist safe to use?
Vulert has no vulnerabilities on record for github.com/circonus-labs/circonusllhist 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/circonus-labs/circonusllhist's Vulert package health score?
Vulert scores github.com/circonus-labs/circonusllhist 49/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/circonus-labs/circonusllhist affected?
No. v0.1.5, 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/circonus-labs/circonusllhist should I use?
v0.1.5 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/circonus-labs/circonusllhist have?
0 vulnerabilities are recorded for github.com/circonus-labs/circonusllhist 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/circonus-labs/circonusllhist vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/circonus-labs/circonusllhist 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/circonus-labs/circonusllhist 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/circonus-labs/circonusllhist for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/circonus-labs/circonusllhist version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.