Vulnerability Database · Go · Package report
github.com/mgechev/dots: vulnerability history, versions and safety
github.com/mgechev/dots 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/mgechev/dots v1.0.0 i
Updated on 23 Oct 2026
Good news: v1.0.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 31 i
- OpenSSF scorecard 2/10 i
- Last release 17 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/mgechev/dots, 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.
- v1.0.0 19 May 2025
- v0.0.0-20250519151913-e27e287cb268 19 May 2025
- v0.0.0-20250519150405-1d20ae333e37 19 May 2025
- v0.0.0-20250519150020-c2ff23ae8dd9 19 May 2025
- v0.0.0-20250519145040-01e7eeb11184 19 May 2025
- v0.0.0-20250518183453-2bf5c7bf6cc0 18 May 2025
- v0.0.0-20250518183358-4d01a5fa42fb 18 May 2025
- v0.0.0-20210922191527-e955255bf517 22 Sep 2021
- v0.0.0-20190921121421-c36f7dcfbb81 21 Sep 2019
- v0.0.0-20181228164730-18fa4c4b71cc 28 Dec 2018
- v0.0.0-20180605013149-8e09d8ea2757 05 Jun 2018
- v0.0.0-20180601024323-3d1c0cc50642 01 Jun 2018
- v0.0.0-20180531000321-1cc1f4773d0c 31 May 2018
- v0.0.0-20180204232027-f7959a15f029 04 Feb 2018
- v0.0.0-20180204205454-fcb6cb4bba78 04 Feb 2018
- v0.0.0-20180204201856-cd05c5e55cc0 04 Feb 2018
All 16 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/mgechev/dots
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/mgechev/dots
Is github.com/mgechev/dots safe to use?
Vulert has no vulnerabilities on record for github.com/mgechev/dots 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/mgechev/dots's Vulert package health score?
Vulert scores github.com/mgechev/dots 56/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/mgechev/dots affected?
No. v1.0.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/mgechev/dots should I use?
v1.0.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/mgechev/dots have?
0 vulnerabilities are recorded for github.com/mgechev/dots 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/mgechev/dots vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/mgechev/dots 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/mgechev/dots 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/mgechev/dots for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mgechev/dots version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.