VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/k-sone/critbitgo: vulnerability history, versions and safety

github.com/k-sone/critbitgo is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/k-sone/critbitgo vulnerabilities

Vulert verdict on github.com/k-sone/critbitgo v1.4.0 i

Updated on 23 Oct 2026

Good news: v1.4.0, the version you would install today, has no known vulnerabilities.

Package health score 42/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on v1.4.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.4.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v1.4.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 47 i
  • OpenSSF scorecard 1/10 i
  • Last release 83 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/k-sone/critbitgo, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.4.1-0.20201217093159-6d9e2448fe95 17 Dec 2020 none MIT — Details →
v0.0.0-20191102005935-4536a49cdb16 02 Nov 2019 none MIT — Details →
v1.4.0 02 Nov 2019 none MIT — Details →
v1.3.1-0.20191024122315-48c9e1530131 24 Oct 2019 none MIT — Details →
v1.3.1-0.20191023123009-164751ab2a6f 23 Oct 2019 none MIT — Details →
v1.3.0 30 Sep 2019 none MIT — Details →
v0.0.0-20180425094137-658116ef1e82 25 Apr 2018 none MIT — Details →
v1.2.0 25 Apr 2018 none MIT — Details →
v1.1.1-0.20180411180838-aa814e944736 11 Apr 2018 none MIT — Details →
v0.0.0-20170112111019-327359a051d7 12 Jan 2017 none MIT — Details →
v1.1.1-0.20170112111019-327359a051d7 12 Jan 2017 none MIT — Details →
v1.1.0 29 Dec 2016 none MIT — Details →
v1.0.1-0.20161227103040-10a0c47e81ad 27 Dec 2016 none MIT — Details →
v1.0.0 02 Apr 2016 none MIT — Details →
v0.0.0-20150327234249-539942900131 27 Mar 2015 none MIT — Details →

All 15 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/k-sone/critbitgo

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/k-sone/critbitgo

Is github.com/k-sone/critbitgo safe to use?

Vulert has no vulnerabilities on record for github.com/k-sone/critbitgo 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/k-sone/critbitgo's Vulert package health score?

Vulert scores github.com/k-sone/critbitgo 42/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/k-sone/critbitgo affected?

No. v1.4.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/k-sone/critbitgo should I use?

v1.4.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/k-sone/critbitgo have?

0 vulnerabilities are recorded for github.com/k-sone/critbitgo 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/k-sone/critbitgo vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/k-sone/critbitgo 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/k-sone/critbitgo 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/k-sone/critbitgo for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/k-sone/critbitgo version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.