VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

whenever: vulnerability history, versions and safety

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

Vulert verdict on whenever 1.1.4 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 1.1.4 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 8,853 i
  • OpenSSF scorecard 3/10 i
  • Last release this month 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 whenever, 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.1.4 21 Oct 2026 none MIT — Details →
1.1.3 15 Sep 2026 none MIT — Details →
1.1.2 18 Jan 2026 none MIT — Details →
1.1.1 08 Dec 2025 none MIT — Details →
1.1.0 21 Nov 2025 none MIT — Details →
1.0.0 13 Jun 2019 none MIT — Details →
0.11.0 23 Apr 2019 none MIT — Details →
0.10.0 20 Nov 2017 none MIT — Details →
0.9.7 14 Jun 2016 none MIT — Details →
0.9.6 13 Jun 2016 none MIT — Details →
0.9.5 12 Jun 2016 none MIT — Details →
0.9.4 24 Oct 2014 none MIT — Details →
0.9.3 05 Oct 2014 none MIT — Details →
0.9.2 04 Mar 2014 none MIT — Details →
0.9.1 03 Mar 2014 none MIT — Details →
0.9.0 18 Dec 2013 none MIT — Details →
0.8.4 23 Jul 2013 none MIT — Details →
0.8.3 11 Jul 2013 none — — Details →
0.8.2 10 Jan 2013 none — — Details →
0.8.1 22 Dec 2012 none — — Details →
0.8.0 08 Nov 2012 none — — Details →
0.7.3 24 Feb 2012 none — — Details →
0.7.2 23 Dec 2011 none — — Details →
0.7.1 20 Dec 2011 none — — Details →
0.7.0 02 Sep 2011 none — — Details →
0.6.8 25 May 2011 none — — Details →
0.6.7 24 Mar 2011 none — — Details →
0.6.6 09 Mar 2011 none — — Details →
0.6.2 26 Oct 2010 none — — Details →
0.6.1 20 Oct 2010 none — — Details →
0.5.3 24 Sep 2010 none — — Details →
0.5.2 16 Sep 2010 none — — Details →
0.5.0 28 Jun 2010 none — — Details →
0.4.2 26 Apr 2010 none — — Details →
0.4.1 30 Nov 2009 none — — Details →
0.4.0 20 Oct 2009 none — — Details →
0.3.7 07 Oct 2009 none — — Details →

All 37 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 whenever

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 whenever

Is whenever safe to use?

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

Vulert scores whenever 84/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 whenever affected?

No. 1.1.4, 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.

How many vulnerabilities does whenever have?

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

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

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