Vulnerability Database · Go · Package report
github.com/radovskyb/watcher: vulnerability history, versions and safety
github.com/radovskyb/watcher 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/radovskyb/watcher v1.0.7 i
Updated on 23 Oct 2026
Good news: v1.0.7, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.0.7 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.7 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.7 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1,506 i
- OpenSSF scorecard 1/10 i
- Last release 86 months ago i
- Licence BSD-3-Clause 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/radovskyb/watcher, 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-20190817010844-f5989f8deca2 17 Aug 2019
- v1.0.7 17 Aug 2019
- v1.0.7-0.20190817010844-f5989f8deca2 17 Aug 2019
- v0.0.0-20190817010809-4b2bb62bcdb1 17 Aug 2019
- v1.0.7-0.20190817003817-37d22d7577d5 17 Aug 2019
- v0.0.0-20190127045435-f33c874a09dc 27 Jan 2019
- v1.0.7-0.20190127045435-f33c874a09dc 27 Jan 2019
- v1.0.6 15 Jan 2019
- v1.0.5 13 Dec 2018
- v1.0.3-0.20181212061845-70a1716c3855 12 Dec 2018
- v1.0.3-0.20181212020837-59f4c5262382 12 Dec 2018
- v0.0.0-20181027232338-25a66c5e3b26 27 Oct 2018
- v1.0.3-0.20181027232338-25a66c5e3b26 27 Oct 2018
- v0.0.0-20180525001723-0d9d32686dbf 25 May 2018
- v1.0.3-0.20180525001723-0d9d32686dbf 25 May 2018
- v1.0.3-0.20180401221139-1d8f9aeb0984 01 Apr 2018
- v0.0.0-20170810063929-6145e1439b9d 10 Aug 2017
- v1.0.2 10 Aug 2017
- v1.0.2-0.20170724060405-eaa2479e35c3 24 Jul 2017
- v1.0.1 21 Jul 2017
- v1.0.0 15 Jun 2017
- v0.0.0-20170524102634-70533d7799ae 24 May 2017
- v0.0.0-20170210035641-828a655184ef 10 Feb 2017
- v0.0.0-20161226044231-1925df70dcfd 26 Dec 2016
- v0.0.0-20161027021150-303d296a5c27 27 Oct 2016
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/radovskyb/watcher
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/radovskyb/watcher
Is github.com/radovskyb/watcher safe to use?
Vulert has no vulnerabilities on record for github.com/radovskyb/watcher 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/radovskyb/watcher's Vulert package health score?
Vulert scores github.com/radovskyb/watcher 55/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/radovskyb/watcher affected?
No. v1.0.7, 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/radovskyb/watcher should I use?
v1.0.7 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/radovskyb/watcher have?
0 vulnerabilities are recorded for github.com/radovskyb/watcher 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/radovskyb/watcher vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/radovskyb/watcher 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/radovskyb/watcher 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/radovskyb/watcher for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/radovskyb/watcher version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.