VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

holidays: vulnerability history, versions and safety

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

Vulert verdict on holidays 11.7.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 11.7.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 879 i
  • OpenSSF scorecard 4/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 holidays, 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
11.7.0 02 Oct 2026 none MIT — Details →
11.6.0 16 Sep 2026 none MIT — Details →
11.5.0 29 Aug 2026 none MIT — Details →
11.4.0 12 Aug 2026 none MIT — Details →
11.3.0 31 Jul 2026 none MIT — Details →
11.2.0 29 Jul 2026 none MIT — Details →
11.1.0 17 Jul 2026 none MIT — Details →
11.0.0 09 Jun 2026 none MIT — Details →
10.0.0 16 May 2026 none MIT — Details →
9.2.0 27 Apr 2026 none MIT — Details →
9.1.2 27 Apr 2026 none MIT — Details →
9.1.1 01 Apr 2026 none MIT — Details →
9.1.0 30 Mar 2026 none MIT — Details →
9.0.0 29 Mar 2026 none MIT — Details →
8.8.0 23 May 2024 none MIT — Details →
8.7.1 30 Dec 2023 none MIT — Details →
8.6.0 15 Sep 2022 none MIT — Details →
8.5.0 05 Jan 2022 none MIT — Details →
8.4.1 06 Jan 2021 none MIT — Details →
8.4.0 24 Dec 2020 none MIT — Details →
8.3.0 14 Jun 2020 none MIT — Details →
8.2.0 28 Apr 2020 none MIT — Details →
8.1.0 10 Jan 2020 none MIT — Details →
8.0.0 25 Sep 2019 none MIT — Details →
7.1.0 03 Feb 2019 none MIT — Details →
7.0.0 09 Dec 2018 none MIT — Details →
6.6.1 13 Oct 2018 none MIT — Details →
6.6.0 01 Oct 2018 none MIT — Details →
6.5.0 21 Sep 2018 none MIT — Details →
6.4.0 06 Mar 2018 none MIT — Details →
6.3.0 13 Jan 2018 none MIT — Details →
6.2.0 09 Oct 2017 none MIT — Details →
6.1.0 15 Aug 2017 none MIT — Details →
6.0.0 01 Aug 2017 none MIT — Details →
5.7.0 16 Jul 2017 none MIT — Details →
5.6.0 03 May 2017 none MIT — Details →
5.5.1 01 May 2017 none MIT — Details →
5.5.0 24 Apr 2017 none MIT — Details →
5.4.0 07 Feb 2017 none MIT — Details →
5.3.0 27 Nov 2016 none MIT — Details →
5.2.1 27 Nov 2016 none MIT — Details →
5.2.0 23 Nov 2016 none MIT — Details →
5.1.0 06 Nov 2016 none MIT — Details →
5.0.0 24 Sep 2016 none MIT — Details →
4.7.0 24 Sep 2016 none MIT — Details →
4.6.0 21 Jul 2016 none MIT — Details →
4.5.0 23 Jun 2016 none MIT — Details →
4.4.0 18 Jun 2016 none MIT — Details →
4.3.0 09 Jun 2016 none MIT — Details →
4.2.0 06 Jun 2016 none MIT — Details →
4.1.0 14 May 2016 none MIT — Details →
4.0.0 23 Apr 2016 none MIT — Details →
3.3.0 17 Apr 2016 none MIT — Details →
3.2.0 21 Feb 2016 none MIT — Details →
3.1.2 05 Jan 2016 none MIT — Details →
3.1.1 22 Dec 2015 none MIT — Details →
3.1.0 20 Dec 2015 none MIT — Details →
3.0.0 13 Dec 2015 none MIT — Details →
2.2.0 25 Jun 2015 none MIT — Details →
2.1.0 23 May 2015 none MIT — Details →
2.0.0 06 Apr 2015 none MIT — Details →
1.2.0 19 Mar 2015 none MIT — Details →
1.1.0 17 Mar 2015 none MIT — Details →
1.0.8 14 Oct 2014 none MIT — Details →
1.0.6 04 Jan 2014 none — — Details →
1.0.5 13 Mar 2012 none — — Details →
1.0.4 19 Oct 2011 none — — Details →
1.0.3 02 Sep 2011 none — — Details →
1.0.2 13 May 2011 none — — Details →
1.0.1 29 Apr 2011 none — — Details →
1.0.0 12 Nov 2010 none — — Details →
0.9.0 25 Jul 2009 none — — Details →
0.9.1 25 Jul 2009 none — — Details →
0.9.2 25 Jul 2009 none — — Details →
0.9.3 25 Jul 2009 none — — Details →

All 75 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 holidays

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 holidays

Is holidays safe to use?

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

Vulert scores holidays 82/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 holidays affected?

No. 11.7.0, 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 holidays should I use?

11.7.0 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 holidays have?

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

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

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