VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

moul.io/progress: vulnerability history, versions and safety

moul.io/progress 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 moul.io/progress vulnerabilities

Vulert verdict on moul.io/progress v1.4.1 i

Updated on 23 Oct 2026

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

Package health score 44/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v1.4.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 12 i
  • OpenSSF scorecard 2/10 i
  • Last release 57 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 moul.io/progress, 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.4.2-0.20220524104232-d715f71afc28 24 May 2022 none Apache-2.0 — Details →
v1.4.2-0.20220417091800-fcb8a823beca 17 Apr 2022 none Apache-2.0 — Details →
v1.4.2-0.20220317192934-6030712955ed 17 Mar 2022 none Apache-2.0 — Details →
v1.4.1 29 Dec 2021 none Apache-2.0 — Details →
v1.4.1-0.20211212135117-6d038153de9d 12 Dec 2021 none Apache-2.0 — Details →
v1.4.1-0.20211127092516-af947c1df07f 27 Nov 2021 none Apache-2.0 — Details →
v1.4.1-0.20210925172612-f533f00b9ad3 25 Sep 2021 none Apache-2.0 — Details →
v1.4.1-0.20210923122749-6e00343c1aa4 23 Sep 2021 none Apache-2.0 — Details →
v1.4.1-0.20210613090806-cfea6e33431b 13 Jun 2021 none Apache-2.0 — Details →
v1.4.1-0.20210517090714-616bdc5beb2b 17 May 2021 none Apache-2.0 — Details →
v1.4.0 19 Apr 2021 none Apache-2.0 — Details →
v1.3.3-0.20210116070505-ae03b91fac18 16 Jan 2021 none Apache-2.0 — Details →
v1.3.2 30 Dec 2020 none Apache-2.0 — Details →
v1.3.1 29 Dec 2020 none Apache-2.0 — Details →
v1.3.0 28 Dec 2020 none Apache-2.0 — Details →
v1.2.0 23 Dec 2020 none Apache-2.0 — Details →
v1.1.0 23 Dec 2020 none Apache-2.0 — Details →
v1.0.0 23 Dec 2020 none Apache-2.0 — Details →

All 18 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 moul.io/progress

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 moul.io/progress

Is moul.io/progress safe to use?

Vulert has no vulnerabilities on record for moul.io/progress 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 moul.io/progress's Vulert package health score?

Vulert scores moul.io/progress 44/100, which reads as risky. 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 moul.io/progress affected?

No. v1.4.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 moul.io/progress should I use?

v1.4.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 moul.io/progress have?

0 vulnerabilities are recorded for moul.io/progress 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 moul.io/progress vulnerabilities disclosed?

0 vulnerabilities were recorded for moul.io/progress 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 moul.io/progress 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 moul.io/progress for upcoming vulnerabilities?

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