Vulnerability Database · Go · Package report
github.com/benbjohnson/clock: vulnerability history, versions and safety
github.com/benbjohnson/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/benbjohnson/clock v1.3.5 i
Updated on 23 Oct 2026
Good news: v1.3.5, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.3.5 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.3.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.3.5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 690 i
- OpenSSF scorecard 3/10 i
- Last release 41 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/benbjohnson/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-20230518034430-fa525c8ac4e6 18 May 2023
- v1.3.6-0.20230518034430-fa525c8ac4e6 18 May 2023
- v1.3.5 18 May 2023
- v1.3.5-0.20230513040314-b675fcb0bb3e 13 May 2023
- v1.3.4 27 Apr 2023
- v1.3.4-0.20230427232111-4362d7026a7b 27 Apr 2023
- v1.3.4-0.20230423172918-2fbf0cb60cfd 23 Apr 2023
- v1.3.3 23 Apr 2023
- v1.3.2-0.20230423170257-023ccf9a0d10 23 Apr 2023
- v1.3.2-0.20230419171841-4dacbdc0eeb0 19 Apr 2023
- v1.3.1 19 Apr 2023
- v1.3.1-0.20230419155104-0ff82de79851 19 Apr 2023
- v0.0.0-20230316063754-419081f64d73 16 Mar 2023
- v1.3.1-0.20230316063754-419081f64d73 16 Mar 2023
- v0.0.0-20230225210953-b9ae427899a1 25 Feb 2023
- v1.3.1-0.20230225210953-b9ae427899a1 25 Feb 2023
- v0.0.0-20220913130405-38e21b7518eb 13 Sep 2022
- v1.3.1-0.20220913130405-38e21b7518eb 13 Sep 2022
- v1.3.1-0.20220412121327-6e4be13a367a 12 Apr 2022
- v1.3.1-0.20211118212106-dcd183e906f1 18 Nov 2021
- v0.0.0-20211115232727-68df829297d4 15 Nov 2021
- v1.2.1-0.20211115232727-68df829297d4 15 Nov 2021
- v1.3.0 15 Nov 2021
- v1.2.1-0.20211112130822-3e4357c3031e 12 Nov 2021
- v1.2.1-0.20211112130408-6754fcb1967b 12 Nov 2021
- v1.2.1-0.20211101152949-5178ebeb0d67 01 Nov 2021
- v1.2.0 01 Nov 2021
- v1.1.1-0.20211029143656-1ae85fe3a88b 29 Oct 2021
- v1.1.1-0.20211029133348-0a12ec5850f9 29 Oct 2021
- v1.1.1-0.20211029133332-eb95674f786d 29 Oct 2021
- v1.1.1-0.20211026183018-47e2ce0429dd 26 Oct 2021
- v1.1.1-0.20211025200506-4378ee033c7d 25 Oct 2021
- v1.1.1-0.20211025180810-5ad814cd9028 25 Oct 2021
- v1.1.1-0.20211025180118-0b9476f99826 25 Oct 2021
- v1.1.1-0.20211025162130-f7a1d13a14c5 25 Oct 2021
- v1.1.1-0.20211020190841-ae809991ac89 20 Oct 2021
- v1.1.1-0.20210213131748-c97fc7b6bee0 13 Feb 2021
- v1.1.1-0.20210212040636-0f43ae616573 12 Feb 2021
- v1.1.1-0.20201127221520-4031354f7760 27 Nov 2020
- v1.1.1-0.20201127194506-9d456ff92b07 27 Nov 2020
- v1.1.0 24 Nov 2020
- v1.0.4-0.20201123203104-421f85866531 23 Nov 2020
- v1.0.3 10 Jun 2020
- v1.0.3-0.20200605000654-6b1ff0d32245 05 Jun 2020
- v1.0.2 18 May 2020
- v1.0.2-0.20200515103758-a528249e8199 15 May 2020
- v1.0.2-0.20200513215328-02a620e7a531 13 May 2020
- v1.0.1 11 May 2020
- v1.0.1-0.20200511141951-dcb3cf9a2a53 11 May 2020
- v1.0.1-0.20200510232254-cf870e30ba58 10 May 2020
- v1.0.1-0.20200510231823-8cd1c9d8c55f 10 May 2020
- v0.0.0-20191108225048-1c0be5eba75f 08 Nov 2019
- v1.0.1-0.20191108225048-1c0be5eba75f 08 Nov 2019
- v1.0.1-0.20191108220815-1c54274ec137 08 Nov 2019
- v0.0.0-20191031141347-6228dc3de676 31 Oct 2019
- v1.0.1-0.20191031141347-6228dc3de676 31 Oct 2019
- v1.0.0 31 Oct 2019
- v0.0.0-20191031122645-fe93a30e1141 31 Oct 2019
- v0.0.0-20161215174838-7dc76406b6d3 15 Dec 2016
- v0.0.0-20160125162948-a620c1cc9866 25 Jan 2016
- v0.0.0-20160125161023-7866f8bac751 25 Jan 2016
- v0.0.0-20160125034407-e75da977388f 25 Jan 2016
- v0.0.0-20150622182828-ae77645379a0 22 Jun 2015
- v0.0.0-20150612171601-c1ed37d73a16 12 Jun 2015
- v0.0.0-20150612165449-7fdf49b9f474 12 Jun 2015
- v0.0.0-20150609024423-52ab87187ce6 09 Jun 2015
- v0.0.0-20150529215208-9534db4666a0 29 May 2015
- v0.0.0-20150529195227-208c64d04cbb 29 May 2015
- v0.0.0-20150528222525-d28830f39ec8 28 May 2015
- v0.0.0-20140827004337-7f9bbfdd12ee 27 Aug 2014
All 70 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/benbjohnson/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/benbjohnson/clock
Is github.com/benbjohnson/clock safe to use?
Vulert has no vulnerabilities on record for github.com/benbjohnson/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/benbjohnson/clock's Vulert package health score?
Vulert scores github.com/benbjohnson/clock 65/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/benbjohnson/clock affected?
No. v1.3.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 github.com/benbjohnson/clock should I use?
v1.3.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 github.com/benbjohnson/clock have?
0 vulnerabilities are recorded for github.com/benbjohnson/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/benbjohnson/clock vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/benbjohnson/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/benbjohnson/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/benbjohnson/clock for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/benbjohnson/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.