VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

calendar-utils: vulnerability history, versions and safety

calendar-utils is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm 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 calendar-utils vulnerabilities

Vulert verdict on calendar-utils 0.12.5 i

Updated on 23 Oct 2026

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

Package health score 64/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release 0.12.5 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Stars 39 i
  • OpenSSF scorecard 2/10 i
  • Last release 7 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, 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 calendar-utils, 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.12.5 19 Mar 2026 none MIT — Details →
0.12.4 01 Sep 2025 none MIT — Details →
0.12.3 01 Sep 2025 none MIT — Details →
0.12.2 27 Aug 2025 none MIT — Details →
0.12.1 27 Aug 2025 none MIT — Details →
0.12.0 25 Aug 2025 none MIT — Details →
0.11.0 09 Oct 2024 none MIT — Details →
0.10.4 14 Oct 2022 none MIT — Details →
0.10.1 02 Aug 2022 none MIT — Details →
0.10.0 02 Aug 2022 none MIT — Details →
0.9.0 12 Nov 2021 none MIT — Details →
0.8.5 13 Aug 2021 none MIT — Details →
0.8.4 12 Jan 2021 none MIT — Details →
0.8.3 20 Oct 2020 none MIT — Details →
0.8.2 12 Sep 2020 none MIT — Details →
0.8.1 17 Jun 2020 none MIT — Details →
0.8.0 03 May 2020 none MIT — Details →
0.7.2 26 Apr 2020 none MIT — Details →
0.7.1 13 Apr 2020 none MIT — Details →
0.7.0 24 Aug 2019 none MIT — Details →
0.6.0 24 Aug 2019 none MIT — Details →
0.5.0 23 Aug 2019 none MIT — Details →
0.4.0 23 Aug 2019 none MIT — Details →
0.3.3 18 Aug 2019 none MIT — Details →
0.3.2 14 Aug 2019 none MIT — Details →
0.3.1 21 Apr 2019 none MIT — Details →
0.3.0 18 Mar 2019 none MIT — Details →
0.3.0-beta.8 17 Mar 2019 none MIT — Details →
0.3.0-beta.7 01 Mar 2019 none MIT — Details →
0.3.0-beta.6 03 Feb 2019 none MIT — Details →
0.2.3 05 Nov 2018 none MIT — Details →
0.3.0-beta.5 05 Nov 2018 none MIT — Details →
0.2.2 14 Oct 2018 none MIT — Details →
0.3.0-beta.4 14 Oct 2018 none MIT — Details →
0.3.0-beta.3 13 Oct 2018 none MIT — Details →
0.3.0-beta.2 09 Oct 2018 none MIT — Details →
0.3.0-beta.1 05 Oct 2018 none MIT — Details →
0.3.0-beta.0 18 Sep 2018 none MIT — Details →
0.2.1 13 Sep 2018 none MIT — Details →
1.0.0-alpha.2 03 Sep 2018 none MIT — Details →
0.2.0 29 Aug 2018 none MIT — Details →
0.2.0-rc.0 06 Aug 2018 none MIT — Details →
0.2.0-alpha.16 28 Jul 2018 none MIT — Details →
0.2.0-alpha.15 27 Jul 2018 none MIT — Details →
0.2.0-alpha.14 19 Jul 2018 none MIT — Details →
0.2.0-alpha.13 11 Jul 2018 none MIT — Details →
0.2.0-alpha.12 23 Jun 2018 none MIT — Details →
0.2.0-alpha.11 23 Jun 2018 none MIT — Details →
0.2.0-alpha.10 22 Jun 2018 none MIT — Details →
0.2.0-alpha.9 22 Jun 2018 none MIT — Details →
0.2.0-alpha.8 22 Jun 2018 none MIT — Details →
0.2.0-alpha.7 18 Jun 2018 none MIT — Details →
0.2.0-alpha.6 18 Jun 2018 none MIT — Details →
0.2.0-alpha.5 10 Jun 2018 none MIT — Details →
0.2.0-alpha.4 10 Jun 2018 none MIT — Details →
0.2.0-alpha.3 10 Jun 2018 none MIT — Details →
0.2.0-alpha.2 10 Jun 2018 none MIT — Details →
0.2.0-alpha.1 10 Jun 2018 none MIT — Details →
0.2.0-alpha.0 10 Jun 2018 none MIT — Details →
1.0.0-alpha.1 17 May 2018 none MIT — Details →
1.0.0-alpha.0 17 May 2018 none MIT — Details →
0.1.2 27 Mar 2018 none MIT — Details →
0.1.1 29 Jan 2018 none MIT — Details →
0.1.0 10 Jan 2018 none MIT — Details →
0.0.60 30 Dec 2017 none MIT — Details →
0.0.59 23 Dec 2017 none MIT — Details →
0.0.58 22 Oct 2017 none MIT — Details →
0.0.57 07 Sep 2017 none MIT — Details →
0.0.56 25 Jun 2017 none MIT — Details →
0.0.55 25 Jun 2017 none MIT — Details →
0.0.54 25 Jun 2017 none MIT — Details →
0.0.53 21 Jun 2017 none MIT — Details →
0.0.52 12 Jun 2017 none MIT — Details →
0.0.51 29 May 2017 none MIT — Details →
0.0.50 29 May 2017 none MIT — Details →
0.0.49 29 May 2017 none MIT — Details →
0.0.48 12 May 2017 none MIT — Details →
0.0.47 12 May 2017 none MIT — Details →
0.0.46 21 Apr 2017 none MIT — Details →
0.0.46-beta.1 21 Apr 2017 none MIT — Details →
0.0.45 10 Apr 2017 none MIT — Details →
0.0.44 09 Apr 2017 none MIT — Details →
0.0.43 25 Mar 2017 none MIT — Details →
0.0.42 21 Mar 2017 none MIT — Details →
0.0.41 12 Mar 2017 none MIT — Details →
0.0.40 10 Mar 2017 none MIT — Details →
0.0.39 09 Dec 2016 none MIT — Details →
0.0.38 05 Dec 2016 none MIT — Details →
0.0.36 31 Oct 2016 none MIT — Details →
0.0.35 30 Oct 2016 none MIT — Details →
0.0.34 29 Oct 2016 none MIT — Details →
0.0.33 13 Oct 2016 none MIT — Details →
0.0.32 08 Oct 2016 none MIT — Details →
0.0.31 07 Oct 2016 none MIT — Details →
0.0.30 05 Oct 2016 none MIT — Details →
0.0.29 05 Oct 2016 none MIT — Details →
0.0.28 25 Sep 2016 none MIT — Details →
0.0.27 24 Sep 2016 none MIT — Details →
0.0.26 23 Sep 2016 none MIT — Details →
0.0.25 10 Sep 2016 none MIT — Details →
0.0.24 10 Sep 2016 none — — Details →
0.0.23 08 Sep 2016 none — — Details →
0.0.22 16 Aug 2016 none — — Details →
0.0.21 16 Aug 2016 none — — Details →
0.0.20 10 Aug 2016 none — — Details →
0.0.19 08 Aug 2016 none — — Details →
0.0.18 05 Aug 2016 none — — Details →
0.0.17 29 Jul 2016 none — — Details →
0.0.16 29 Jul 2016 none — — Details →
0.0.15 25 Jul 2016 none — — Details →
0.0.14 25 Jul 2016 none — — Details →
0.0.13 24 Jul 2016 none — — Details →
0.0.12 24 Jul 2016 none — — Details →
0.0.11 24 Jul 2016 none — — Details →
0.0.10 24 Jul 2016 none — — Details →
0.0.9 16 Jul 2016 none — — Details →
0.0.8 11 Jul 2016 none — — Details →
0.0.7 04 Jul 2016 none — — Details →
0.0.6 03 Jul 2016 none — — Details →
0.0.5 03 Jul 2016 none — — Details →

The newest 120 of 124 versions Vulert tracks. 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 calendar-utils

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 calendar-utils

Is calendar-utils safe to use?

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

Vulert scores calendar-utils 64/100, which reads as usable, but worth attention. 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 calendar-utils affected?

No. 0.12.5, 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 calendar-utils should I use?

0.12.5 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 calendar-utils have?

0 vulnerabilities are recorded for calendar-utils in the npm 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 calendar-utils vulnerabilities disclosed?

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

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