VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/mholt/acmez: vulnerability history, versions and safety

github.com/mholt/acmez 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/mholt/acmez vulnerabilities

Vulert verdict on github.com/mholt/acmez v1.2.0 i

Updated on 23 Oct 2026

Good news: v1.2.0, the version you would install today, has no known vulnerabilities.

Package health score 57/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

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

  • Current release v1.2.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 354 i
  • OpenSSF scorecard 2/10 i
  • Last release 40 months ago i
  • Licence Apache-2.0 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/mholt/acmez, 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
v1.2.1-0.20240327225408-10574a763fe1 27 Mar 2024 none Apache-2.0 — Details →
v1.2.1-0.20240308161508-c0dcf7bf3865 08 Mar 2024 none Apache-2.0 — Details →
v1.2.1-0.20240222185419-10d0fd9f6805 22 Feb 2024 none Apache-2.0 — Details →
v1.2.1-0.20240222032837-c5645f1099f3 22 Feb 2024 none Apache-2.0 — Details →
v1.2.1-0.20240218034401-47c159b3f0f3 18 Feb 2024 none Apache-2.0 — Details →
v1.2.1-0.20240213224109-ef82f2683689 13 Feb 2024 none Apache-2.0 — Details →
v1.2.1-0.20231121215345-422d0ad3b732 21 Nov 2023 none Apache-2.0 — Details →
v1.2.1-0.20230829173812-ee0926b59e18 29 Aug 2023 none Apache-2.0 — Details →
v1.2.0 20 Jun 2023 none Apache-2.0 — Details →
v1.1.2-0.20230619185816-5ae23acfbc37 19 Jun 2023 none Apache-2.0 — Details →
v0.0.0-20230609032614-d65f20562864 09 Jun 2023 none Apache-2.0 — Details →
v1.1.2-0.20230609032614-d65f20562864 09 Jun 2023 none Apache-2.0 — Details →
v1.1.1 06 May 2023 none Apache-2.0 — Details →
v1.1.1-0.20230410175320-d2a3d7e78082 10 Apr 2023 none Apache-2.0 — Details →
v1.1.0 10 Feb 2023 none Apache-2.0 — Details →
v1.0.5-0.20230208220554-77a0cda67aea 08 Feb 2023 none Apache-2.0 — Details →
v1.0.5-0.20221205190119-67b31c739c61 05 Dec 2022 none Apache-2.0 — Details →
v1.0.5-0.20220906203200-d79cc20fee91 06 Sep 2022 none Apache-2.0 — Details →
v1.0.4 02 Aug 2022 none Apache-2.0 — Details →
v1.0.4-0.20220725164406-dbb5d0c1d220 25 Jul 2022 none Apache-2.0 — Details →
v1.0.3 05 Jul 2022 none Apache-2.0 — Details →
v1.0.3-0.20220402091049-0a77cb061c7d 02 Apr 2022 none Apache-2.0 — Details →
v1.0.3-0.20220306172641-4b14f803e964 06 Mar 2022 none Apache-2.0 — Details →
v1.0.2 02 Feb 2022 none Apache-2.0 — Details →
v1.0.1 08 Nov 2021 none Apache-2.0 — Details →
v1.0.0 26 Aug 2021 none Apache-2.0 — Details →
v0.1.3 23 Jan 2021 none Apache-2.0 — Details →
v0.1.2 04 Jan 2021 none Apache-2.0 — Details →
v0.1.2-0.20210104214829-eb3552473230 04 Jan 2021 none Apache-2.0 — Details →
v0.1.2-0.20201206182414-c2aed85cb023 06 Dec 2020 none Apache-2.0 — Details →
v0.1.1 11 Aug 2020 none Apache-2.0 — Details →
v0.1.1-0.20200811184240-dc9c5f05ed1e 11 Aug 2020 none Apache-2.0 — Details →
v0.1.1-0.20200810215816-dbe88fc6cf09 10 Aug 2020 none Apache-2.0 — Details →
v0.1.1-0.20200810191759-2511a6e975e3 10 Aug 2020 none Apache-2.0 — Details →
v0.1.0 30 Jul 2020 none Apache-2.0 — Details →
v0.0.0-20200729231307-5ae67956ef6f 29 Jul 2020 none Apache-2.0 — Details →
v0.0.0-20200729145521-e5fde8a7673c 29 Jul 2020 none Apache-2.0 — Details →
v0.0.0-20200727220025-4d718f4df0cf 27 Jul 2020 none Apache-2.0 — Details →
v0.0.0-20200727173234-36df02d41145 27 Jul 2020 none Apache-2.0 — Details →

All 39 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/mholt/acmez

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/mholt/acmez

Is github.com/mholt/acmez safe to use?

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

Vulert scores github.com/mholt/acmez 57/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/mholt/acmez affected?

No. v1.2.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/mholt/acmez should I use?

v1.2.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/mholt/acmez have?

0 vulnerabilities are recorded for github.com/mholt/acmez 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/mholt/acmez vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/mholt/acmez 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/mholt/acmez 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/mholt/acmez for upcoming vulnerabilities?

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