Vulnerability Database · Go · Package report

github.com/robfig/cron/v3: vulnerability history, versions and safety

github.com/robfig/cron/v3 is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go 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.

Vulert verdict on github.com/robfig/cron/v3 v3.0.1 i

Updated on 23 Oct 2026

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

Package health score 62/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release v3.0.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 14,193 i
  • OpenSSF scorecard 1/10 i
  • Last release 81 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/robfig/cron/v3, 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
v3.0.0-20210106135023-bc59245fe10e 06 Jan 2021 none MIT — Details →
v3.0.2-0.20210106135023-bc59245fe10e 06 Jan 2021 none MIT — Details →
v3.0.2-0.20200518143530-6a8421bcff44 18 May 2020 none MIT — Details →
v3.0.2-0.20200316182343-208b4f76bfdd 16 Mar 2020 none MIT — Details →
v3.0.2-0.20200104014708-e7da914f1b8a 04 Jan 2020 none MIT — Details →
v3.0.0-20200104010508-ccba498c397b 04 Jan 2020 none MIT — Details →
v3.0.1 04 Jan 2020 none MIT — Details →
v3.0.1-0.20200104010508-ccba498c397b 04 Jan 2020 none MIT — Details →
v3.0.1-0.20191217031834-3d516ccad133 17 Dec 2019 none MIT — Details →
v3.0.1-0.20191125210756-b7cc47d857a8 25 Nov 2019 none MIT — Details →
v3.0.0-20190716002318-e843a09e5b2d 16 Jul 2019 none MIT — Details →
v3.0.1-0.20190716002318-e843a09e5b2d 16 Jul 2019 none MIT — Details →
v3.0.1-0.20190712112536-bfc372e108e4 12 Jul 2019 none MIT — Details →
v3.0.1-0.20190712074740-fa682d18e04d 12 Jul 2019 none MIT — Details →
v3.0.0 11 Jul 2019 none MIT — Details →
v3.0.0-20190711170238-45fbe1491cdd 11 Jul 2019 none MIT — Details →
v3.0.0-rc1.0.20190711161735-43863da9e008 11 Jul 2019 none MIT — Details →
v3.0.0-rc1.0.20190711114904-1cba5e61f90e 11 Jul 2019 none MIT — Details →
v3.0.0-rc1.0.20190617022103-07c22694e4a0 17 Jun 2019 none MIT — Details →
v3.0.0-20190617021521-e4fa405d9559 17 Jun 2019 none MIT — Details →
v3.0.0-rc1.0.20190617021521-e4fa405d9559 17 Jun 2019 none MIT — Details →
v3.0.0-rc1.0.20190616225207-70971dc81bab 16 Jun 2019 none MIT — Details →
v3.0.0-20190503020742-0f01e6b177f4 03 May 2019 none MIT — Details →
v3.0.0-rc1 03 May 2019 none MIT — Details →
v3.0.0-20190311224149-605d51319cbb 11 Mar 2019 none MIT — Details →
v3.0.0-20190213023936-dbf322045545 13 Feb 2019 none MIT — Details →
v3.0.0-20190212223444-4813ba249658 12 Feb 2019 none MIT — Details →
v3.0.0-20190212222657-eeecf155fcb0 12 Feb 2019 none MIT — Details →
v3.0.0-20190210194926-1e507e218b68 10 Feb 2019 none MIT — Details →

All 29 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 github.com/robfig/cron/v3

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 github.com/robfig/cron/v3

Is github.com/robfig/cron/v3 safe to use?

Vulert has no vulnerabilities on record for github.com/robfig/cron/v3 in Go 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 github.com/robfig/cron/v3's Vulert package health score?

Vulert scores github.com/robfig/cron/v3 62/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 github.com/robfig/cron/v3 affected?

No. v3.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 github.com/robfig/cron/v3 should I use?

v3.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 github.com/robfig/cron/v3 have?

0 vulnerabilities are recorded for github.com/robfig/cron/v3 in the Go 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 github.com/robfig/cron/v3 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/robfig/cron/v3 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 github.com/robfig/cron/v3 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 github.com/robfig/cron/v3 for upcoming vulnerabilities?

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