VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/emersion/go-message: vulnerability history, versions and safety

github.com/emersion/go-message is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/emersion/go-message vulnerabilities

Vulert verdict on github.com/emersion/go-message v0.18.2 i

Updated on 23 Oct 2026

Good news: v0.18.2, the version you would install today, has no known vulnerabilities.

Package health score 64/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

What to do: Stay on v0.18.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.18.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.18.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 458 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/emersion/go-message, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20250216181611-b9039e0d248f 16 Feb 2025 none MIT — Details →
v0.18.3-0.20250216181611-b9039e0d248f 16 Feb 2025 none MIT — Details →
v0.18.3-0.20250113214739-162c13400467 13 Jan 2025 none MIT — Details →
v0.18.2-0.20250103231503-5336cde63124 03 Jan 2025 none MIT — Details →
v0.18.3-0.20250103231503-5336cde63124 03 Jan 2025 none MIT — Details →
v0.18.2-0.20241222122955-46f63d44ba9d 22 Dec 2024 none MIT — Details →
v0.18.2 28 Sep 2024 none MIT — Details →
v0.18.2-0.20240928145753-6a718fa6214f 28 Sep 2024 none MIT — Details →
v0.0.0-20240713135450-acf41e649f9a 13 Jul 2024 none MIT — Details →
v0.18.2-0.20240713135450-acf41e649f9a 13 Jul 2024 none MIT — Details →
v0.18.1 06 Mar 2024 none MIT — Details →
v0.18.1-0.20240306143358-f7e55c42f6e9 06 Mar 2024 none MIT — Details →
v0.18.1-0.20240303204659-c2ff70fd20da 03 Mar 2024 none MIT — Details →
v0.18.1-0.20240125080931-de399d8ca26f 25 Jan 2024 none MIT — Details →
v0.18.0 10 Jan 2024 none MIT — Details →
v0.17.0 27 Aug 2023 none MIT — Details →
v0.16.1-0.20230815062633-ea300cac569f 15 Aug 2023 none MIT — Details →
v0.16.1-0.20230721154854-f80b76e0eed4 21 Jul 2023 none MIT — Details →
v0.16.1-0.20230615112147-4a149f74ea15 15 Jun 2023 none MIT — Details →
v0.16.1-0.20230311175701-67aae7bf1c09 11 Mar 2023 none MIT — Details →
v0.0.0-20230213130619-56fd0ba3ffba 13 Feb 2023 none MIT — Details →
v0.16.1-0.20230213130619-56fd0ba3ffba 13 Feb 2023 none MIT — Details →
v0.16.1-0.20220912191637-7840c643b9a8 12 Sep 2022 none MIT — Details →
v0.16.1-0.20220822203423-e8f6c2ea0f35 22 Aug 2022 none MIT — Details →
v0.16.0 26 May 2022 none MIT — Details →
v0.15.1-0.20220511142650-21cb40cb7be3 11 May 2022 none MIT — Details →
v0.15.1-0.20220131103555-e8079699eb3a 31 Jan 2022 none MIT — Details →
v0.15.1-0.20211127104534-c2fc7ed7540b 27 Nov 2021 none MIT — Details →
v0.15.1-0.20211006080919-f217430d6d4a 06 Oct 2021 none MIT — Details →
v0.15.0 11 Jun 2021 none MIT — Details →
v0.14.2-0.20210506100537-b5087f96b449 06 May 2021 none MIT — Details →
v0.0.0-20210222181244-981888ca7c08 22 Feb 2021 none MIT — Details →
v0.14.1-0.20210222181244-981888ca7c08 22 Feb 2021 none MIT — Details →
v0.14.2-0.20210222181244-981888ca7c08 22 Feb 2021 none MIT — Details →
v0.14.2-0.20210115145036-b27fd96b0a98 15 Jan 2021 none MIT — Details →
v0.14.1-0.20201223130831-5b0c10070943 23 Dec 2020 none MIT — Details →
v0.12.1-0.20201221184100-40c3f864532b 21 Dec 2020 none MIT — Details →
v0.14.1 21 Dec 2020 none MIT — Details →
v0.14.1-0.20201221184100-40c3f864532b 21 Dec 2020 none MIT — Details →
v0.14.1-0.20201214163959-5a87ff483d9a 14 Dec 2020 none MIT — Details →
v0.14.1-0.20201128174606-dc7aaacbc735 28 Nov 2020 none MIT — Details →
v0.14.0 25 Nov 2020 none MIT — Details →
v0.13.1-0.20201112194930-f77964fe28bd 12 Nov 2020 none MIT — Details →
v0.13.1-0.20201109222432-61b8de525812 09 Nov 2020 none MIT — Details →
v0.13.1-0.20201026220603-eb8e213ccf1b 26 Oct 2020 none MIT — Details →
v0.13.0 26 Oct 2020 none MIT — Details →
v0.12.1-0.20200903165315-e1abe21f389a 03 Sep 2020 none MIT — Details →
v0.12.1-0.20200902094549-410ea5ee4c4b 02 Sep 2020 none MIT — Details →
v0.12.1-0.20200824204225-9094bd0b8bc0 24 Aug 2020 none MIT — Details →
v0.12.1-0.20200824164219-4500fbb11f59 24 Aug 2020 none MIT — Details →
v0.12.1-0.20200811092405-d3c4f157949e 11 Aug 2020 none MIT — Details →
v0.12.1-0.20200622123527-6f75db93daa5 22 Jun 2020 none MIT — Details →
v0.12.0 28 May 2020 none MIT — Details →
v0.11.3-0.20200525094746-5b97b1bcd112 25 May 2020 none MIT — Details →
v0.11.3-0.20200429151259-c5125629c3f8 29 Apr 2020 none MIT — Details →
v0.11.3-0.20200422153910-8c6ac6b57e3d 22 Apr 2020 none MIT — Details →
v0.11.2 15 Apr 2020 none MIT — Details →
v0.11.2-0.20200215191609-9c4415ed8676 15 Feb 2020 none MIT — Details →
v0.11.2-0.20200206103857-46fe03ddefcb 06 Feb 2020 none MIT — Details →
v0.11.2-0.20200123123926-40e7be64e63c 23 Jan 2020 none MIT — Details →
v0.11.1 06 Jan 2020 none MIT — Details →
v0.11.1-0.20191229143723-71005f4b31f3 29 Dec 2019 none MIT — Details →
v0.11.0 19 Dec 2019 none MIT — Details →
v0.0.0-20191116124005-65fd0119e899 16 Nov 2019 none MIT — Details →
v0.10.9-0.20191116124005-65fd0119e899 16 Nov 2019 none MIT — Details →
v0.10.8 16 Oct 2019 none MIT — Details →
v0.10.8-0.20191016211634-85cd354f5485 16 Oct 2019 none MIT — Details →
v0.10.8-0.20190917204513-66913d529826 17 Sep 2019 none MIT — Details →
v0.10.8-0.20190830183645-45550ec58166 30 Aug 2019 none MIT — Details →
v0.10.7 19 Aug 2019 none MIT — Details →
v0.10.6 13 Aug 2019 none MIT — Details →
v0.10.6-0.20190731140552-b6482e3b3769 31 Jul 2019 none MIT — Details →
v0.10.5 27 Jul 2019 none MIT — Details →
v0.10.4 09 Jul 2019 none MIT — Details →
v0.10.4-0.20190609204914-5c83a6521b32 09 Jun 2019 none MIT — Details →
v0.10.4-0.20190609165112-592ace5bc1ca 09 Jun 2019 none MIT — Details →
v0.10.3 18 May 2019 none MIT — Details →
v0.10.2 14 May 2019 none MIT — Details →
v0.10.2-0.20190514201857-604a73722993 14 May 2019 none MIT — Details →
v0.10.1 14 May 2019 none MIT — Details →
v0.10.0 14 May 2019 none MIT — Details →
v0.0.0-20180928092003-63ac8399c1e4 28 Sep 2018 none MIT — Details →
v0.9.2 28 Sep 2018 none MIT — Details →
v0.9.2-0.20180928091115-36be220535c7 28 Sep 2018 none MIT — Details →
v0.0.0-20180321173051-51445bfdc558 21 Mar 2018 none MIT — Details →
v0.9.2-0.20180321173051-51445bfdc558 21 Mar 2018 none MIT — Details →
v0.0.0-20180321064743-9b004c277ed8 21 Mar 2018 none MIT — Details →
v0.9.2-0.20180321064743-9b004c277ed8 21 Mar 2018 none MIT — Details →
v0.9.1 09 Feb 2018 none MIT — Details →
v0.0.0-20171212113934-54e13462a96d 12 Dec 2017 none MIT — Details →
v0.0.0-20171114092213-6110082ee43c 14 Nov 2017 none MIT — Details →
v0.0.0-20170918151215-901dbfdd5a44 18 Sep 2017 none MIT — Details →
v0.0.0-20170802224156-1716e3f473f9 02 Aug 2017 none MIT — Details →
v0.0.0-20170708134827-2e3e63ce56d5 08 Jul 2017 none MIT — Details →
v0.0.0-20170603074648-3e802f3218ec 03 Jun 2017 none MIT — Details →
v0.0.0-20170208195734-9ee49becf2c6 08 Feb 2017 none MIT — Details →
v0.0.0-20170126144826-9f9a0938b9ea 26 Jan 2017 none MIT — Details →
v0.0.0-20170126104157-06415ec3eb6f 26 Jan 2017 none MIT — Details →
v0.0.0-20170108113226-25ef30a4a17e 08 Jan 2017 none MIT — Details →

All 99 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/emersion/go-message

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/emersion/go-message

Is github.com/emersion/go-message safe to use?

Vulert has no vulnerabilities on record for github.com/emersion/go-message 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/emersion/go-message's Vulert package health score?

Vulert scores github.com/emersion/go-message 64/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/emersion/go-message affected?

No. v0.18.2, 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/emersion/go-message should I use?

v0.18.2 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/emersion/go-message have?

0 vulnerabilities are recorded for github.com/emersion/go-message 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/emersion/go-message vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/emersion/go-message 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/emersion/go-message 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/emersion/go-message for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/emersion/go-message version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.