VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

debug: vulnerability history, versions and safety

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

Vulert verdict on debug 1.11.1 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

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

01 Versions

Which versions are affected

Every version Vulert tracks for debug, 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
1.11.1 19 Dec 2025 none Ruby — Details →
1.11.0 17 Jun 2025 none Ruby — Details →
1.10.0 18 Dec 2024 none Ruby — Details →
1.9.2 29 Mar 2024 none Ruby — Details →
1.9.1 22 Dec 2023 none Ruby — Details →
1.9.0 11 Dec 2023 none Ruby — Details →
1.8.0 09 May 2023 none Ruby — Details →
1.7.2 28 Mar 2023 none Ruby — Details →
1.7.1 22 Dec 2022 none Ruby — Details →
1.7.0 02 Dec 2022 none Ruby — Details →
1.6.3 24 Oct 2022 none Ruby — Details →
1.6.2 10 Aug 2022 none Ruby — Details →
1.6.1 13 Jul 2022 none Ruby — Details →
1.6.0 11 Jul 2022 none Ruby — Details →
1.5.0 30 Mar 2022 none Ruby — Details →
1.4.0 17 Dec 2021 none Ruby — Details →
0.2.1 11 Nov 2021 none Ruby — Details →
1.3.4 29 Oct 2021 none Ruby — Details →
1.3.3 29 Oct 2021 none Ruby — Details →
1.3.2 28 Oct 2021 none Ruby — Details →
1.3.1 22 Oct 2021 none Ruby — Details →
1.3.0 20 Oct 2021 none Ruby — Details →
1.2.4 05 Oct 2021 none Ruby — Details →
1.2.3 05 Oct 2021 none Ruby — Details →
1.2.2 01 Oct 2021 none Ruby — Details →
1.2.1 30 Sep 2021 none Ruby — Details →
1.2.0 29 Sep 2021 none Ruby — Details →
1.1.0 14 Sep 2021 none Ruby — Details →
1.0.0 08 Sep 2021 none Ruby — Details →
1.0.0.rc2 03 Sep 2021 none Ruby — Details →
1.0.0.rc1 03 Sep 2021 none Ruby — Details →
1.0.0.beta8 14 Jul 2021 none Ruby — Details →
1.0.0.beta7 13 Jul 2021 none Ruby — Details →
1.0.0.beta6 07 Jul 2021 none Ruby — Details →
1.0.0.beta5 17 Jun 2021 none Ruby — Details →
1.0.0.beta4 25 May 2021 none Ruby — Details →
1.0.0.beta3 14 May 2021 none Ruby — Details →
1.0.0.beta2 10 May 2021 none Ruby — Details →
1.0.0.beta1 07 May 2021 none Ruby — Details →
1.0.0.alpha1 07 Apr 2021 none MIT — Details →
1.0.0.alpha0 07 Apr 2021 none MIT — Details →
0.2.0 17 Mar 2021 none Ruby — Details →

All 42 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 debug

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 debug

Is debug safe to use?

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

Vulert scores debug 78/100, which reads as in good shape. 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 debug affected?

No. 1.11.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 debug should I use?

1.11.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 debug have?

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

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

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