VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

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

Vulert verdict on github.com/mholt/acmez/v3 v3.1.7 i

Updated on 23 Oct 2026

Good news: v3.1.7, the version you would install today, has no known vulnerabilities.

Package health score 72/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release v3.1.7 — 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 this month 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/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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v3.1.7 25 Sep 2026 none Apache-2.0 — Details →
v3.1.7-0.20260806175713-e289d7faf819 06 Aug 2026 none Apache-2.0 — Details →
v3.1.7-0.20260309215101-8f633102409d 09 Mar 2026 none Apache-2.0 — Details →
v3.1.6 20 Feb 2026 none Apache-2.0 — Details →
v3.1.5 12 Feb 2026 none Apache-2.0 — Details →
v3.1.5-0.20260212163645-ddffee86f127 12 Feb 2026 none Apache-2.0 — Details →
v3.1.5-0.20260112234720-d34f7bb1ce6a 12 Jan 2026 none Apache-2.0 — Details →
v3.1.5-0.20251217042301-dfd32054dd91 17 Dec 2025 none Apache-2.0 — Details →
v3.1.4 26 Sep 2025 none Apache-2.0 — Details →
v3.1.4-0.20250924181656-8706f5405f9e 24 Sep 2025 none Apache-2.0 — Details →
v3.1.3 03 Sep 2025 none Apache-2.0 — Details →
v3.1.3-0.20250903215752-3d27c5c34a75 03 Sep 2025 none Apache-2.0 — Details →
v3.1.3-0.20250826170449-56e23df9585b 26 Aug 2025 none Apache-2.0 — Details →
v3.1.3-0.20250823034226-e9bc05663df3 23 Aug 2025 none Apache-2.0 — Details →
v3.1.3-0.20250707230716-df105ba17a10 07 Jul 2025 none Apache-2.0 — Details →
v3.1.2 01 Apr 2025 none Apache-2.0 — Details →
v3.1.1 24 Mar 2025 none Apache-2.0 — Details →
v3.1.1-0.20250314204006-a7dc0b74c0dd 14 Mar 2025 none Apache-2.0 — Details →
v3.0.2-0.20250303172830-90fead83847c 03 Mar 2025 none Apache-2.0 — Details →
v3.1.0 03 Mar 2025 none Apache-2.0 — Details →
v3.0.2-0.20250127200334-04a702faaf36 27 Jan 2025 none Apache-2.0 — Details →
v3.0.1 09 Jan 2025 none Apache-2.0 — Details →
v3.0.0 14 Dec 2024 none Apache-2.0 — Details →
v3.0.0-20241214053340-45433dfc1161 14 Dec 2024 none Apache-2.0 — Details →
v3.0.0-20241205212901-02868f041e58 05 Dec 2024 none Apache-2.0 — Details →

All 25 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/v3

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/v3

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

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

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

No. v3.1.7, 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/v3 should I use?

v3.1.7 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/v3 have?

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

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

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/mholt/acmez/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.