Vulnerability Database · RubyGems · Package report

racc: vulnerability history, versions and safety

Q: How do I monitor racc for upcoming vulnerabilities?

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

racc 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 racc vulnerabilities

Vulert verdict on racc 1.8.1 i

Updated on 23 Oct 2026

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

Package health score 65/100

Security Minor issues
Maintenance Slowing
Popularity Widely used
Community Quiet

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

Current release 1.8.1 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 569 i
OpenSSF scorecard 4/10 i
Last release 26 months ago i
Licence Ruby 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 racc, 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.8.1	30 Jul 2024	none	Ruby	—	Details →
1.8.0	20 May 2024	none	Ruby	—	Details →
1.7.3	04 Nov 2023	none	Ruby	—	Details →
1.7.3.pre.1	03 Nov 2023	none	Ruby	—	Details →
1.7.2	01 Nov 2023	none	Ruby	—	Details →
1.7.1	14 Jun 2023	none	Ruby	—	Details →
1.7.0	08 Jun 2023	none	Ruby	—	Details →
1.6.2	23 Dec 2022	none	Ruby	—	Details →
1.6.1	05 Dec 2022	none	Ruby	—	Details →
1.6.0	19 Oct 2021	none	Ruby	—	Details →
1.5.2	26 Dec 2020	none	Ruby	—	Details →
1.5.1	10 Nov 2020	none	Ruby	—	Details →
1.5.0	25 Mar 2020	none	MIT	—	Details →
1.4.16	10 Dec 2019	none	MIT	—	Details →
1.4.15	27 Feb 2019	none	MIT	—	Details →
1.4.14	25 Nov 2015	none	MIT	—	Details →
1.4.13	16 Oct 2015	none	MIT	—	Details →
1.4.12	26 Aug 2014	none	MIT	—	Details →
1.4.11	08 Jan 2014	none	MIT	—	Details →
1.4.10	16 Oct 2013	none	—	—	Details →
1.4.9	07 Aug 2012	none	—	—	Details →
1.4.8	02 Mar 2012	none	—	—	Details →
1.4.7	19 Oct 2011	none	—	—	Details →
1.4.6	25 Jul 2009	none	—	—	Details →

All 24 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 racc

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 racc

Is racc safe to use?

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

Vulert scores racc 65/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 racc affected?

No. 1.8.1, 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 racc should I use?

1.8.1 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 racc have?

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

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

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