Vulnerability Database · Go · Package report
github.com/ThreeDotsLabs/watermill-sql/v3: vulnerability history, versions and safety
github.com/ThreeDotsLabs/watermill-sql/v3 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.
See all github.com/ThreeDotsLabs/watermill-sql/v3 vulnerabilities
Vulert verdict on github.com/ThreeDotsLabs/watermill-sql/v3 v3.1.0 i
Updated on 23 Oct 2026
Good news: v3.1.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Niche
- Community Quiet
What to do: Stay on v3.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v3.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v3.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 94 i
- OpenSSF scorecard 2/10 i
- Last release 24 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/ThreeDotsLabs/watermill-sql/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.
- v3.1.1-0.20241017154019-7fb34fb6d66a 17 Oct 2024
- v3.1.1-0.20241011111920-9b207ae2da1c 11 Oct 2024
- v3.0.4-0.20240924144637-c35e7e4f94f1 24 Sep 2024
- v3.1.0 24 Sep 2024
- v3.0.4-0.20240924105125-694caf646991 24 Sep 2024
- v3.0.4-0.20240924054727-03810ecacad4 24 Sep 2024
- v3.0.4-0.20240906133734-187e31f5ed36 06 Sep 2024
- v3.0.4-0.20240906122508-e0de57ad1d8e 06 Sep 2024
- v3.0.4-0.20240906121730-aaf911c0adb7 06 Sep 2024
- v3.0.4-0.20240906121631-62f93534b600 06 Sep 2024
- v3.0.4-0.20240906121028-f42a4cbde116 06 Sep 2024
- v3.0.4-0.20240906115919-b00f99a56e28 06 Sep 2024
- v3.0.4-0.20240906104507-0298e7283633 06 Sep 2024
- v3.0.4-0.20240830132306-ec03c337ea28 30 Aug 2024
- v3.0.3 28 Aug 2024
- v3.0.2 23 Aug 2024
- v3.0.2-0.20240823183518-66690416f116 23 Aug 2024
- v3.0.1 28 Mar 2024
- v3.0.1-0.20240328192519-938906b10275 28 Mar 2024
- v3.0.0 19 Dec 2023
- v3.0.0-20231219154753-ff18e90eb049 19 Dec 2023
- v3.0.0-20231123150416-ca7703dad4c6 23 Nov 2023
All 22 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/ThreeDotsLabs/watermill-sql/v3
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/ThreeDotsLabs/watermill-sql/v3
Is github.com/ThreeDotsLabs/watermill-sql/v3 safe to use?
Vulert has no vulnerabilities on record for github.com/ThreeDotsLabs/watermill-sql/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/ThreeDotsLabs/watermill-sql/v3's Vulert package health score?
Vulert scores github.com/ThreeDotsLabs/watermill-sql/v3 63/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/ThreeDotsLabs/watermill-sql/v3 affected?
No. v3.1.0, 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/ThreeDotsLabs/watermill-sql/v3 should I use?
v3.1.0 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/ThreeDotsLabs/watermill-sql/v3 have?
0 vulnerabilities are recorded for github.com/ThreeDotsLabs/watermill-sql/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/ThreeDotsLabs/watermill-sql/v3 vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/ThreeDotsLabs/watermill-sql/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/ThreeDotsLabs/watermill-sql/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/ThreeDotsLabs/watermill-sql/v3 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/ThreeDotsLabs/watermill-sql/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.