VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

modernc.org/mathutil: vulnerability history, versions and safety

modernc.org/mathutil 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 modernc.org/mathutil vulnerabilities

Vulert verdict on modernc.org/mathutil v1.7.1 i

Updated on 23 Oct 2026

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

Package health score 65/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v1.7.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 4 i
  • Last release 21 months ago i
  • Licence BSD-3-Clause 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 modernc.org/mathutil, 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.7.1 26 Dec 2024 none BSD-3-Clause — Details →
v1.7.1-0.20241226121325-28129eec384c 26 Dec 2024 none BSD-3-Clause — Details →
v1.6.1-0.20241026114214-f4adddaa84a7 26 Oct 2024 none BSD-3-Clause — Details →
v1.7.0 26 Oct 2024 none BSD-3-Clause — Details →
v1.5.1-0.20230621150831-aabd79189264 21 Jun 2023 none BSD-3-Clause — Details →
v1.6.0 21 Jun 2023 none BSD-3-Clause — Details →
v1.1.2-0.20220822142738-b13e5b564332 22 Aug 2022 none BSD-3-Clause — Details →
v1.4.2-0.20220822142738-45297b8131f5 22 Aug 2022 none BSD-3-Clause — Details →
v1.4.2-0.20220822142738-b13e5b564332 22 Aug 2022 none BSD-3-Clause — Details →
v1.5.0 22 Aug 2022 none BSD-3-Clause — Details →
v1.4.1 21 Jun 2021 none BSD-3-Clause — Details →
v1.4.0 23 May 2021 none BSD-3-Clause — Details →
v1.3.1 23 May 2021 none BSD-3-Clause — Details →
v1.3.0 23 May 2021 none BSD-3-Clause — Details →
v0.0.0-20210121151200-19b10d78032b 21 Jan 2021 none BSD-3-Clause — Details →
v1.2.2 21 Jan 2021 none BSD-3-Clause — Details →
v1.2.1 20 Dec 2020 none BSD-3-Clause — Details →
v1.2.0 19 Dec 2020 none BSD-3-Clause — Details →
v1.1.2-0.20201219164820-129e6f306ac6 19 Dec 2020 none BSD-3-Clause — Details →
v0.0.0-20200411161111-2a1ec3875312 11 Apr 2020 none BSD-3-Clause — Details →
v1.1.1 11 Apr 2020 none BSD-3-Clause — Details →
v0.0.0-20200127163748-fdc8e2b54814 27 Jan 2020 none BSD-3-Clause — Details →
v1.1.0 27 Jan 2020 none BSD-3-Clause — Details →
v1.0.1-0.20181109151725-3f082a4bce87 09 Nov 2018 none BSD-3-Clause — Details →
v1.0.0 06 Nov 2018 none BSD-3-Clause — Details →
v0.0.0-20181021201202-eba54fb065b7 21 Oct 2018 none BSD-3-Clause — Details →
v0.0.0-20180504122225-ca4c9f2c1369 04 May 2018 none BSD-3-Clause — Details →
v0.0.0-20180221133535-7764e6a2216a 21 Feb 2018 none BSD-3-Clause — Details →
v0.0.0-20180214153908-5455a562bccb 14 Feb 2018 none BSD-3-Clause — Details →
v0.0.0-20180103181919-c90ba19bea89 03 Jan 2018 none BSD-3-Clause — Details →
v0.0.0-20171015093839-09cde8d5df5f 15 Oct 2017 none BSD-3-Clause — Details →
v0.0.0-20170901165910-91af0ce59d17 01 Sep 2017 none BSD-3-Clause — Details →
v0.0.0-20170621181044-6baf61e03170 21 Jun 2017 none BSD-3-Clause — Details →
v0.0.0-20170313102836-1447ad269d64 13 Mar 2017 none BSD-3-Clause — Details →
v0.0.0-20161012104533-4609a45a9e61 12 Oct 2016 none BSD-3-Clause — Details →
v0.0.0-20160613104831-78ad7f262603 13 Jun 2016 none BSD-3-Clause — Details →
v0.0.0-20160119163116-38a5fe05cd94 19 Jan 2016 none BSD-3-Clause — Details →
v0.0.0-20150605115324-a804f0f2d852 05 Jun 2015 none BSD-3-Clause — Details →
v0.0.0-20150216133129-f9551431b78e 16 Feb 2015 none BSD-3-Clause — Details →
v0.0.0-20150118111314-250d0b9d3304 18 Jan 2015 none BSD-3-Clause — Details →

All 40 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 modernc.org/mathutil

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 modernc.org/mathutil

Is modernc.org/mathutil safe to use?

Vulert has no vulnerabilities on record for modernc.org/mathutil 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 modernc.org/mathutil's Vulert package health score?

Vulert scores modernc.org/mathutil 65/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 modernc.org/mathutil affected?

No. v1.7.1, 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 modernc.org/mathutil should I use?

v1.7.1 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 modernc.org/mathutil have?

0 vulnerabilities are recorded for modernc.org/mathutil 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 modernc.org/mathutil vulnerabilities disclosed?

0 vulnerabilities were recorded for modernc.org/mathutil 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 modernc.org/mathutil 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 modernc.org/mathutil for upcoming vulnerabilities?

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