VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

chronic: vulnerability history, versions and safety

chronic is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems 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 chronic vulnerabilities

Vulert verdict on chronic 0.10.2 i

Updated on 23 Oct 2026

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

Package health score 67/100
  • Security No known security issues
  • Maintenance Unmaintained
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 0.10.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 157 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, 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 chronic, 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
0.10.2 09 Sep 2013 none MIT — Details →
0.10.1 27 Aug 2013 none MIT — Details →
0.10.0 25 Aug 2013 none MIT — Details →
0.9.1 25 Feb 2013 none — — Details →
0.9.0 21 Dec 2012 none — — Details →
0.8.0 16 Sep 2012 none — — Details →
0.7.0 01 Aug 2012 none — — Details →
0.6.7 01 Feb 2012 none — — Details →
0.6.6 23 Nov 2011 none — — Details →
0.6.5 05 Nov 2011 none — — Details →
0.6.4 09 Sep 2011 none — — Details →
0.6.3 02 Sep 2011 none — — Details →
0.6.2 28 Jul 2011 none — — Details →
0.6.1 21 Jul 2011 none — — Details →
0.6.0 19 Jul 2011 none — — Details →
0.5.0 01 Jul 2011 none — — Details →
0.4.4 12 Jun 2011 none — — Details →
0.4.3 08 Jun 2011 none — — Details →
0.4.2 07 Jun 2011 none — — Details →
0.4.1 05 Jun 2011 none — — Details →
0.4.0 04 Jun 2011 none — — Details →
0.3.0 22 Oct 2010 none — — Details →
0.1.0 25 Jul 2009 none — — Details →
0.1.1 25 Jul 2009 none — — Details →
0.1.2 25 Jul 2009 none — — Details →
0.1.3 25 Jul 2009 none — — Details →
0.1.4 25 Jul 2009 none — — Details →
0.1.5 25 Jul 2009 none — — Details →
0.1.6 25 Jul 2009 none — — Details →
0.2.0 25 Jul 2009 none — — Details →
0.2.1 25 Jul 2009 none — — Details →
0.2.2 25 Jul 2009 none — — Details →
0.2.3 25 Jul 2009 none — — Details →

All 33 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 chronic

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 chronic

Is chronic safe to use?

Vulert has no vulnerabilities on record for chronic in RubyGems 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 chronic's Vulert package health score?

Vulert scores chronic 67/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 chronic affected?

No. 0.10.2, 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 chronic should I use?

0.10.2 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 chronic have?

0 vulnerabilities are recorded for chronic in the RubyGems 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 chronic vulnerabilities disclosed?

0 vulnerabilities were recorded for chronic 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 chronic 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 chronic for upcoming vulnerabilities?

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