VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

debase-ruby_core_source: vulnerability history, versions and safety

debase-ruby_core_source 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 debase-ruby_core_source vulnerabilities

Vulert verdict on debase-ruby_core_source 4.0.1 i

Updated on 23 Oct 2026

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

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

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

  • Current release 4.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 4 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 debase-ruby_core_source, 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
4.1.0.preview1 14 Oct 2026 none MIT — Details →
4.0.1 01 Jun 2026 none MIT — Details →
4.0.0 05 Jan 2026 none MIT — Details →
4.0.0.preview2 18 Nov 2025 none MIT — Details →
3.4.1 13 Jan 2025 none MIT — Details →
3.3.6 10 Oct 2024 none MIT — Details →
3.3.5 03 Oct 2024 none MIT — Details →
3.3.1 09 Jan 2024 none MIT — Details →
3.3.0 26 Dec 2023 none MIT — Details →
3.2.3 25 Nov 2023 none MIT — Details →
3.2.2 18 Sep 2023 none MIT — Details →
3.2.1 24 May 2023 none MIT — Details →
3.2.0 25 Dec 2022 none MIT — Details →
0.10.18 28 Nov 2022 none MIT — Details →
0.10.17 09 Sep 2022 none MIT — Details →
0.10.16 19 May 2022 none MIT — Details →
0.10.15 05 Apr 2022 none MIT — Details →
0.10.14 27 Dec 2021 none MIT — Details →
0.10.13 22 Nov 2021 none MIT — Details →
0.10.12 12 Jan 2021 none MIT — Details →
0.10.11 27 Sep 2020 none MIT — Details →
0.10.10 28 Aug 2020 none MIT — Details →
0.10.9 27 Dec 2019 none MIT — Details →
0.10.8 02 Dec 2019 none MIT — Details →
0.10.7 14 Nov 2019 none MIT — Details →
0.10.6 07 Oct 2019 none MIT — Details →
0.10.5 07 Jun 2019 none MIT — Details →
0.10.4 25 Dec 2018 none MIT — Details →
0.10.3 30 Apr 2018 none MIT — Details →
0.10.2 26 Dec 2017 none MIT — Details →
0.10.1 15 Dec 2017 none MIT — Details →
0.10.0 08 Nov 2017 none MIT — Details →
0.9.11 17 Oct 2017 none MIT — Details →
0.9.10 14 Sep 2017 none MIT — Details →
0.9.9 30 Mar 2017 none MIT — Details →
0.9.8 29 Mar 2017 none MIT — Details →
0.9.7 23 Mar 2017 none MIT — Details →
0.9.6 25 Dec 2016 none MIT — Details →
0.9.5 12 Dec 2016 none MIT — Details →
0.9.4 21 Nov 2016 none MIT — Details →
0.9.3 16 Nov 2016 none MIT — Details →
0.9.2 10 Sep 2016 none MIT — Details →
0.9.1 20 Jun 2016 none MIT — Details →
0.9.0 28 Apr 2016 none MIT — Details →
0.8.6 01 Apr 2016 none MIT — Details →
0.8.5 31 Mar 2016 none MIT — Details →
0.8.4 25 Dec 2015 none MIT — Details →
0.8.3 16 Dec 2015 none MIT — Details →
0.8.2 11 Dec 2015 none MIT — Details →
0.8.1 12 Nov 2015 none MIT — Details →
0.8.0 08 Oct 2015 none MIT — Details →
0.7.10 19 Aug 2015 none MIT — Details →
0.7.9 14 Apr 2015 none MIT — Details →
0.7.8 13 Mar 2015 none MIT — Details →
0.7.7 05 Mar 2015 none MIT — Details →
0.7.6 05 Mar 2015 none MIT — Details →
0.7.5 25 Dec 2014 none MIT — Details →
0.7.4 19 Dec 2014 none MIT — Details →
0.7.3 04 Dec 2014 none MIT — Details →
0.7.2 14 Nov 2014 none MIT — Details →
0.7.1 28 Oct 2014 none MIT — Details →
0.6.0 03 Oct 2014 none MIT — Details →
0.5.0 03 Oct 2014 none MIT — Details →
0.4.0 25 Sep 2014 none MIT — Details →
0.3.0 25 Sep 2014 none MIT — Details →
0.2.0 25 Sep 2014 none MIT — Details →
0.1.0 25 Sep 2014 none MIT — Details →

All 67 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 debase-ruby_core_source

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 debase-ruby_core_source

Is debase-ruby_core_source safe to use?

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

Vulert scores debase-ruby_core_source 94/100, which reads as healthy. 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 debase-ruby_core_source affected?

No. 4.0.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 debase-ruby_core_source should I use?

4.0.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 debase-ruby_core_source have?

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

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

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