Vulnerability Database · Go · Package report
github.com/juju/clock: vulnerability history, versions and safety
github.com/juju/clock is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/juju/clock v1.1.1 i
Updated on 23 Oct 2026
Good news: v1.1.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 13 i
- OpenSSF scorecard 2/10 i
- Last release 27 months ago i
- Licence LGPL-3.0 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/juju/clock, 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.
- v0.0.0-20240703042217-20b89efe043f 03 Jul 2024
- v1.1.1 03 Jul 2024
- v1.1.1-0.20240703042217-20b89efe043f 03 Jul 2024
- v1.1.0 03 Jul 2024
- v1.0.4-0.20240703033711-c4d7d79755ab 03 Jul 2024
- v1.0.3 20 Jan 2023
- v1.0.3-0.20230120050744-18a29fa28e18 20 Jan 2023
- v1.0.2 08 Aug 2022
- v1.0.1 08 Aug 2022
- v0.0.0-20220807072521-176b0b79412c 07 Aug 2022
- v0.0.0-20220806115431-a302a9c3bdfe 06 Aug 2022
- v0.0.0-20220704231616-a2b96c8eeb27 04 Jul 2022
- v1.0.0 04 Jul 2022
- v0.0.0-20220203021603-d9deb868a28a 03 Feb 2022
- v0.0.0-20220203021241-3192acf6ddb5 03 Feb 2022
- v0.0.0-20220202072423-1b0f830854c4 02 Feb 2022
- v0.0.0-20190205081909-9c5c9712527c 05 Feb 2019
- v0.0.0-20190205033648-021c4c73ef75 05 Feb 2019
- v0.0.0-20190204150615-308b53124bbf 04 Feb 2019
- v0.0.0-20190203075248-8b60cf4746f3 03 Feb 2019
- v0.0.0-20180808021310-bab88fc67299 08 Aug 2018
- v0.0.0-20180808014805-8994b06547ba 08 Aug 2018
- v0.0.0-20180524022203-d293bb356ca4 24 May 2018
- v0.0.0-20180524021710-7361de57fded 24 May 2018
- v0.0.0-20180524011530-a116594d5c98 24 May 2018
All 25 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/juju/clock
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
Questions
About github.com/juju/clock
Is github.com/juju/clock safe to use?
Vulert has no vulnerabilities on record for github.com/juju/clock 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/juju/clock's Vulert package health score?
Vulert scores github.com/juju/clock 50/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/juju/clock affected?
No. v1.1.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/juju/clock should I use?
v1.1.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/juju/clock have?
0 vulnerabilities are recorded for github.com/juju/clock 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/juju/clock vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/juju/clock 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/juju/clock 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/juju/clock for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/juju/clock version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.