VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

concurrent-ruby-edge: vulnerability history, versions and safety

concurrent-ruby-edge 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 concurrent-ruby-edge vulnerabilities

Vulert verdict on concurrent-ruby-edge 0.7.2 i

Updated on 23 Oct 2026

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

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

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

  • Current release 0.7.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 21 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 concurrent-ruby-edge, 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.7.2 15 Jan 2025 none MIT — Details →
0.7.1 07 Jun 2024 none MIT — Details →
0.7.0 23 Jan 2023 none MIT — Details →
0.6.0 10 Feb 2020 none MIT — Details →
0.6.0.pre1 26 Jan 2020 none MIT — Details →
0.5.0 11 Mar 2019 none MIT — Details →
0.4.1 05 Nov 2018 none MIT — Details →
0.4.0.pre2 18 Sep 2018 none MIT — Details →
0.4.0.pre1 15 Aug 2018 none MIT — Details →
0.2.4 29 Mar 2017 none MIT — Details →
0.3.1 26 Feb 2017 none MIT — Details →
0.3.0 27 Dec 2016 none MIT — Details →
0.2.3 17 Dec 2016 none MIT — Details →
0.2.3.pre3 23 Jun 2016 none MIT — Details →
0.2.2 02 May 2016 none MIT — Details →
0.2.1 27 Feb 2016 none MIT — Details →
0.2.0 13 Nov 2015 none MIT — Details →
0.2.0.pre5 05 Nov 2015 none MIT — Details →
0.1.2 04 Nov 2015 none MIT — Details →
0.2.0.pre4 08 Oct 2015 none MIT — Details →
0.2.0.pre3 30 Sep 2015 none MIT — Details →
0.2.0.pre2 19 Sep 2015 none MIT — Details →
0.2.0.pre1 19 Aug 2015 none MIT — Details →
0.1.1 09 Aug 2015 none MIT — Details →
0.1.0 10 Jul 2015 none MIT — Details →
0.1.0.pre3 22 Jun 2015 none MIT — Details →
0.1.0.pre2 08 Jun 2015 none MIT — Details →

All 27 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 concurrent-ruby-edge

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 concurrent-ruby-edge

Is concurrent-ruby-edge safe to use?

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

Vulert scores concurrent-ruby-edge 87/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 concurrent-ruby-edge affected?

No. 0.7.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 concurrent-ruby-edge should I use?

0.7.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 concurrent-ruby-edge have?

0 vulnerabilities are recorded for concurrent-ruby-edge 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 concurrent-ruby-edge vulnerabilities disclosed?

0 vulnerabilities were recorded for concurrent-ruby-edge 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 concurrent-ruby-edge 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 concurrent-ruby-edge for upcoming vulnerabilities?

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