Vulnerability Database · Go · Package report
github.com/armon/circbuf: vulnerability history, versions and safety
github.com/armon/circbuf 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/armon/circbuf v0.0.0-20190214190532-5111143e8da2 i
Updated on 23 Oct 2026
Good news: v0.0.0-20190214190532-5111143e8da2, 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.0.0-20190214190532-5111143e8da2 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20190214190532-5111143e8da2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20190214190532-5111143e8da2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 175 i
- OpenSSF scorecard 1/10 i
- Last release 92 months ago i
- Licence MIT 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/armon/circbuf, 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-20190214190532-5111143e8da2 14 Feb 2019
- v0.0.0-20190213212447-2523937c7508 13 Feb 2019
- v0.0.0-20150827004946-bbbad097214e 27 Aug 2015
- v0.0.0-20140502180025-f092b4f207b6 02 May 2014
- v0.0.0-20140502174951-0c64c003e8e0 02 May 2014
- v0.0.0-20140429221844-6489c3264276 29 Apr 2014
- v0.0.0-20140429205548-b263a58ad4b3 29 Apr 2014
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| v0.0.0-20190214190532-5111143e8da2 | 14 Feb 2019 | none | MIT | — | Details → |
| v0.0.0-20190213212447-2523937c7508 | 13 Feb 2019 | none | MIT | — | Details → |
| v0.0.0-20150827004946-bbbad097214e | 27 Aug 2015 | none | MIT | — | Details → |
| v0.0.0-20140502180025-f092b4f207b6 | 02 May 2014 | none | MIT | — | Details → |
| v0.0.0-20140502174951-0c64c003e8e0 | 02 May 2014 | none | MIT | — | Details → |
| v0.0.0-20140429221844-6489c3264276 | 29 Apr 2014 | none | MIT | — | Details → |
| v0.0.0-20140429205548-b263a58ad4b3 | 29 Apr 2014 | none | MIT | — | Details → |
All 7 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/armon/circbuf
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/armon/circbuf
Is github.com/armon/circbuf safe to use?
Vulert has no vulnerabilities on record for github.com/armon/circbuf 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/armon/circbuf's Vulert package health score?
Vulert scores github.com/armon/circbuf 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/armon/circbuf affected?
No. v0.0.0-20190214190532-5111143e8da2, 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/armon/circbuf should I use?
v0.0.0-20190214190532-5111143e8da2 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/armon/circbuf have?
0 vulnerabilities are recorded for github.com/armon/circbuf 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/armon/circbuf vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/armon/circbuf 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/armon/circbuf 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/armon/circbuf for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/armon/circbuf version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.