Vulnerability Database · RubyGems · Package report

coderay: vulnerability history, versions and safety

Q: How do I monitor coderay for upcoming vulnerabilities?

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

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

0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all coderay vulnerabilities

Vulert verdict on coderay 1.1.3 i

Updated on 23 Oct 2026

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

Package health score 55/100

Security Minor issues
Maintenance Unmaintained
Popularity Widely used
Community Quiet

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

Current release 1.1.3 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 866 i
OpenSSF scorecard 1/10 i
Last release 76 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for coderay, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
1.1.3	30 May 2020	none	MIT	—	Details →
1.1.3.rc1	30 May 2020	none	MIT	—	Details →
1.1.2	03 Sep 2017	none	MIT	—	Details →
1.1.2.rc1	03 Sep 2017	none	MIT	—	Details →
1.1.1	20 Feb 2016	none	MIT	—	Details →
1.1.1.rc1	13 Feb 2016	none	MIT	—	Details →
1.1.0	31 Aug 2013	none	MIT	—	Details →
1.1.0.rc5	30 Aug 2013	none	MIT	—	Details →
1.1.0.rc4	23 Aug 2013	none	MIT	—	Details →
1.1.0.rc3	25 Jul 2013	none	MIT	—	Details →
1.1.0.rc2	14 Jul 2013	none	MIT	—	Details →
1.1.0.rc1	13 Jul 2013	none	MIT	—	Details →
1.0.9	20 Feb 2013	none	MIT	—	Details →
1.0.9.rc1	17 Feb 2013	none	MIT	—	Details →
1.0.8	07 Oct 2012	none	—	—	Details →
1.0.8.rc1	07 Oct 2012	none	—	—	Details →
1.0.7	25 Jun 2012	none	—	—	Details →
1.0.7.rc2	19 Jun 2012	none	—	—	Details →
1.0.7.rc1	05 Apr 2012	none	—	—	Details →
1.0.6	05 Apr 2012	none	—	—	Details →
1.0.6.rc1	01 Apr 2012	none	—	—	Details →
1.0.5	27 Dec 2011	none	—	—	Details →
1.0.5.rc1	27 Dec 2011	none	—	—	Details →
1.0.4	02 Nov 2011	none	—	—	Details →
1.0.3	26 Oct 2011	none	—	—	Details →
1.0.2	26 Oct 2011	none	—	—	Details →
1.0.1	19 Oct 2011	none	—	—	Details →
1.0.0	21 Sep 2011	none	—	—	Details →
1.0.0.864rc3	19 Sep 2011	none	—	—	Details →
1.0.0.846rc2	08 Sep 2011	none	—	—	Details →
1.0.0.835rc1	29 Aug 2011	none	—	—	Details →
1.0.0.831pre	23 Aug 2011	none	—	—	Details →
1.0.0.815pre	19 Aug 2011	none	—	—	Details →
1.0.0.800pre	09 Jul 2011	none	—	—	Details →
1.0.0.798.pre	08 Jul 2011	none	—	—	Details →
1.0.0.788.pre	25 Jun 2011	none	—	—	Details →
1.0.0.778.pre	12 Jun 2011	none	—	—	Details →
0.9.8	01 May 2011	none	—	—	Details →
0.9.8.pre	30 Apr 2011	none	—	—	Details →
1.0.0.738.pre	12 Apr 2011	none	—	—	Details →
0.9.7	15 Jan 2011	none	—	—	Details →
0.9.7.pre	14 Jan 2011	none	—	—	Details →
0.9.6	25 Nov 2010	none	—	—	Details →
0.9.6.pre2	20 Nov 2010	none	—	—	Details →
0.9.6.pre	11 Oct 2010	none	—	—	Details →
0.9.5	28 Sep 2010	none	—	—	Details →
0.9.4	31 Aug 2010	none	—	—	Details →
1.0.0.598.pre	11 Jun 2010	none	—	—	Details →
0.9.3	19 Apr 2010	none	—	—	Details →
0.9.2	14 Mar 2010	none	—	—	Details →
0.9.1	01 Jan 2010	none	—	—	Details →
0.8.357	02 Oct 2009	none	—	—	Details →
0.4.3.48	25 Jul 2009	none	—	—	Details →
0.4.5.73	25 Jul 2009	none	—	—	Details →
0.5.0.100	25 Jul 2009	none	—	—	Details →
0.5.0.115	25 Jul 2009	none	—	—	Details →
0.5.0.121	25 Jul 2009	none	—	—	Details →
0.7.1.147	25 Jul 2009	none	—	—	Details →
0.7.2.165	25 Jul 2009	none	—	—	Details →
0.7.2.168	25 Jul 2009	none	—	—	Details →
0.7.2.176	25 Jul 2009	none	—	—	Details →
0.7.4.196	25 Jul 2009	none	—	—	Details →
0.7.4.215	25 Jul 2009	none	—	—	Details →
0.8.260	25 Jul 2009	none	—	—	Details →
0.8.263	25 Jul 2009	none	—	—	Details →
0.8.270	25 Jul 2009	none	—	—	Details →
0.8.273	25 Jul 2009	none	—	—	Details →
0.8.303	25 Jul 2009	none	—	—	Details →
0.8.312	25 Jul 2009	none	—	—	Details →

All 69 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for coderay

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 coderay

Is coderay safe to use?

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

Vulert scores coderay 55/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 coderay affected?

No. 1.1.3, 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 coderay should I use?

1.1.3 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 coderay have?

0 vulnerabilities are recorded for coderay 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 coderay vulnerabilities disclosed?

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

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