Vulnerability Database · Go · Package report
github.com/emicklei/dot: vulnerability history, versions and safety
github.com/emicklei/dot 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/emicklei/dot v1.11.0 i
Updated on 23 Oct 2026
Good news: v1.11.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v1.11.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.11.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.11.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 299 i
- OpenSSF scorecard 3/10 i
- Last release 8 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/emicklei/dot, 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.11.1-0.20260530144559-73b6a0221bfe 30 May 2026
- v0.0.0-20260421091725-20ceb2738b74 21 Apr 2026
- v1.11.1-0.20260421091725-20ceb2738b74 21 Apr 2026
- v1.11.0 07 Feb 2026
- v1.10.0 03 Dec 2025
- v1.9.2 07 Oct 2025
- v1.9.2-0.20250915074725-cc10c09582d5 15 Sep 2025
- v0.0.0-20250914180555-c803cf523fe7 14 Sep 2025
- v1.9.1 14 Sep 2025
- v1.8.1-0.20250728111408-6eb95e12cb6d 28 Jul 2025
- v1.9.0 28 Jul 2025
- v1.8.1-0.20250725130841-491db7f62cc3 25 Jul 2025
- v1.8.0 10 Mar 2025
- v1.7.0 28 Feb 2025
- v1.6.4 02 Dec 2024
- v1.6.3 14 Nov 2024
- v1.6.3-0.20241114142004-04052ec013cc 14 Nov 2024
- v1.6.3-0.20240722095526-c2eeec053c7e 22 Jul 2024
- v1.6.3-0.20240430051221-274cbb84e758 30 Apr 2024
- v1.6.2 15 Apr 2024
- v1.6.2-0.20240224135930-0f82f7522f68 24 Feb 2024
- v1.6.1 17 Jan 2024
- v1.6.1-0.20240117210026-23be7e5ccd7b 17 Jan 2024
- v1.6.0 30 Jul 2023
- v1.5.1-0.20230724202708-f4693e29ecb6 24 Jul 2023
- v1.5.1-0.20230723201452-beeaffa7abfc 23 Jul 2023
- v1.5.1-0.20230722193910-6964ed74e26e 22 Jul 2023
- v1.5.0 20 Jun 2023
- v1.4.2 28 Mar 2023
- v1.4.1 28 Mar 2023
- v1.4.0 28 Mar 2023
- v1.3.1 21 Feb 2023
- v1.3.0 30 Jan 2023
- v1.2.0 18 Nov 2022
- v1.1.1-0.20221117104514-b6ff15f7224c 17 Nov 2022
- v1.1.0 07 Nov 2022
- v1.0.1-0.20221102123412-fa7c7d1b2d14 02 Nov 2022
- v1.0.0 22 Jun 2022
- v0.16.1-0.20210609134347-cd3c2c1cf436 09 Jun 2021
- v0.16.1-0.20210609121144-abc8294031b4 09 Jun 2021
- v0.16.1-0.20210609120332-c6288994cf76 09 Jun 2021
- v0.16.1-0.20210607082845-f606061d1f64 07 Jun 2021
- v0.16.0 04 May 2021
- v0.15.1-0.20201030120858-a78a7231f070 30 Oct 2020
- v0.15.0 30 Oct 2020
- v0.14.1-0.20201018122453-966008b949b7 18 Oct 2020
- v0.14.1-0.20200916133321-98f44b4529ae 16 Sep 2020
- v0.14.0 25 Aug 2020
- v0.13.0 24 Aug 2020
- v0.12.0 21 Aug 2020
- v0.11.0 16 May 2020
- v0.10.3-0.20200514114743-324e876f5d42 14 May 2020
- v0.0.0-20200131063231-5810de2f2ab7 31 Jan 2020
- v0.10.2 31 Jan 2020
- v0.0.0-20190814074732-f4a04130244d 14 Aug 2019
- v0.10.1 14 Aug 2019
- v0.10.0 29 May 2019
- v0.9.3 15 Apr 2019
- v0.9.2 09 Feb 2019
- v0.9.1 09 Feb 2019
- v0.9.1-0.20190122094014-55d3f7ff1061 22 Jan 2019
- v0.9.0 17 Jan 2019
- v0.8.0 02 Jun 2018
- v0.0.0-20160120123922-1d6e39dd3996 20 Jan 2016
All 64 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/emicklei/dot
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/emicklei/dot
Is github.com/emicklei/dot safe to use?
Vulert has no vulnerabilities on record for github.com/emicklei/dot 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/emicklei/dot's Vulert package health score?
Vulert scores github.com/emicklei/dot 70/100, which reads as in good shape. 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/emicklei/dot affected?
No. v1.11.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/emicklei/dot should I use?
v1.11.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/emicklei/dot have?
0 vulnerabilities are recorded for github.com/emicklei/dot 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/emicklei/dot vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/emicklei/dot 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/emicklei/dot 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/emicklei/dot for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/emicklei/dot version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.