Vulnerability Database · Go · Package report

github.com/nothub/mrpack-install: vulnerability history, versions and safety

github.com/nothub/mrpack-install is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 64 releases, from Feb 2023 to Aug 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
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.

Vulert verdict on github.com/nothub/mrpack-install v0.16.10 i

Updated on 23 Oct 2026

Action needed: v0.16.10 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 66/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Inactive

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v0.16.10 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 20 Aug 2024 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Stars 329 i
  • Last release 32 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/nothub/mrpack-install, 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.21.0-beta.0.20260311001147-480907b4ede3 11 Mar 2026 H1 U1 MIT Yes Details →
v0.21.0-beta.0.20251208225720-15827b708d2e 08 Dec 2025 H1 U1 MIT Yes Details →
v0.21.0-beta.0.20250913194843-f9b20d32ab59 13 Sep 2025 H1 U1 MIT Yes Details →
v0.21.0-beta 14 Jun 2025 H1 U1 MIT Yes Details →
v0.20.0-beta.0.20250221115245-74dea552d0e3 21 Feb 2025 H1 U1 MIT Yes Details →
v0.20.0-beta 13 Feb 2025 H1 U1 MIT Yes Details →
v0.19.0-beta.0.20250125142752-96bfe0992c6a 25 Jan 2025 H1 U1 MIT Yes Details →
v0.19.0-beta 25 Jan 2025 H1 U1 MIT Yes Details →
v0.18.2-beta.0.20241124165411-3363dcb5671f 24 Nov 2024 H1 U1 MIT Yes Details →
v0.18.2-beta.0.20241110133808-08cab2d09469 10 Nov 2024 H1 U1 MIT Yes Details →
v0.18.2-beta.0.20241026093246-470ed5f66d64 26 Oct 2024 H1 U1 MIT Yes Details →
v0.18.1-beta.0.20241026085115-a4dad0dddcb7 26 Oct 2024 H1 U1 MIT Yes Details →
v0.18.2-beta 26 Oct 2024 H1 U1 MIT Yes Details →
v0.18.0-beta.0.20241019140109-f393b067e2ab 19 Oct 2024 H1 U1 MIT Yes Details →
v0.18.1-beta 19 Oct 2024 H1 U1 MIT Yes Details →
v0.17.3-beta.0.20241019134610-0acab52ec0cc 19 Oct 2024 H1 U1 MIT Yes Details →
v0.18.0-beta 19 Oct 2024 H1 U1 MIT Yes Details →
v0.17.3-beta.0.20240619113603-b93185cbba26 19 Jun 2024 H1 U1 MIT Yes Details →
v0.17.3-beta.0.20240525231759-eccd3889c9a6 25 May 2024 H1 U1 MIT Yes Details →
v0.17.2-beta.0.20240525214051-e01f0da6c269 25 May 2024 H1 U1 MIT Yes Details →
v0.17.3-beta 25 May 2024 H1 U1 MIT Yes Details →
v0.17.2-beta.0.20240518094723-398cce4e12bd 18 May 2024 H1 U1 MIT Yes Details →
v0.17.1-beta.0.20240505111709-20549fc8274f 05 May 2024 H1 U1 MIT Yes Details →
v0.17.2-beta 05 May 2024 H1 U1 MIT Yes Details →
v0.17.0-beta.0.20240505105845-ce06ea7ad057 05 May 2024 H1 U1 MIT Yes Details →
v0.17.1-beta 05 May 2024 H1 U1 MIT Yes Details →
v0.16.5-0.20240402222855-c3a83c7750c1 02 Apr 2024 H1 U1 MIT Yes Details →
v0.17.0-indev.0.20240319151730-a5601b66d3d4 19 Mar 2024 H1 U1 MIT Yes Details →
v0.17.0-indev.0.20240316184532-8acc8c051c30 16 Mar 2024 H1 U1 MIT Yes Details →
v0.16.11-0.20240210133724-624e89929825 10 Feb 2024 H1 U1 MIT Yes Details →
v0.16.10 10 Feb 2024 H1 U1 MIT Yes Details →
v0.16.5-0.20231031230930-19cc5b0d5129 31 Oct 2023 H1 U1 MIT Yes Details →
v0.16.9 31 Oct 2023 H1 U1 MIT Yes Details →
v0.16.5-0.20230909004827-898da256f3db 09 Sep 2023 H1 U1 MIT Yes Details →
v0.16.8 08 Sep 2023 H1 U1 MIT Yes Details →
v0.16.5-0.20230804152345-23c15cae5a71 04 Aug 2023 H1 U1 MIT Yes Details →
v0.16.8-0.20230515163930-f5656cf91f48 15 May 2023 H1 U1 MIT Yes Details →
v0.16.7 15 May 2023 H1 U1 MIT Yes Details →
v0.16.6 15 May 2023 H1 U1 MIT Yes Details →
v0.16.5 18 Feb 2023 H1 U1 MIT Yes Details →
v0.16.4 02 Feb 2023 H1 U1 MIT Yes Details →
v0.16.3 31 Jan 2023 H1 U1 MIT Yes Details →
v0.16.2 14 Nov 2022 H1 U1 MIT Yes Details →
v0.16.1 20 Sep 2022 H1 U1 MIT Yes Details →
v0.16.1-0.20220918184724-ad43fc35a7ea 18 Sep 2022 H1 U1 MIT Yes Details →
v0.16.0 18 Sep 2022 H1 U1 MIT Yes Details →
v0.15.2 10 Sep 2022 H1 U1 MIT Yes Details →
v0.15.1 10 Sep 2022 H1 U1 MIT Yes Details →
v0.15.0 10 Sep 2022 H1 U1 MIT Yes Details →
v0.14.0 07 Sep 2022 H1 U1 MIT Yes Details →
v0.13.1-0.20220907193025-9b4c1d07007d 07 Sep 2022 H1 U1 MIT Yes Details →
v0.13.0 07 Sep 2022 H1 U1 MIT Yes Details →
v0.12.0 07 Sep 2022 H1 U1 MIT Yes Details →
v0.11.0 06 Sep 2022 H1 U1 MIT Yes Details →
v0.10.4 04 Sep 2022 H1 U1 MIT Yes Details →
v0.10.3 03 Sep 2022 H1 U1 MIT Yes Details →
v0.10.2 03 Sep 2022 H1 U1 MIT Yes Details →
v0.10.1 03 Sep 2022 H1 U1 MIT Yes Details →
v0.10.1-0.20220903184908-c14be673b05d 03 Sep 2022 H1 U1 MIT Yes Details →
v0.10.0 03 Sep 2022 H1 U1 MIT Yes Details →
v0.9.1 03 Sep 2022 H1 U1 MIT Yes Details →
v0.9.0 03 Sep 2022 H1 U1 MIT Yes Details →
v0.8.0 03 Sep 2022 H1 U1 MIT Yes Details →
v0.7.0 03 Sep 2022 H1 U1 MIT Yes Details →

All 64 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2023 1
  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/nothub/mrpack-install

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

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/nothub/mrpack-install

Is github.com/nothub/mrpack-install safe to use?

Vulert records 2 vulnerabilities for github.com/nothub/mrpack-install in Go: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/nothub/mrpack-install's Vulert package health score?

Vulert scores github.com/nothub/mrpack-install 66/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/nothub/mrpack-install affected?

Yes. v0.16.10, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/nothub/mrpack-install should I use?

v0.16.10 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/nothub/mrpack-install have?

2 vulnerabilities are recorded for github.com/nothub/mrpack-install in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/nothub/mrpack-install vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/nothub/mrpack-install in the last 12 months, and the oldest entry in this database dates to 08 Feb 2023. 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/nothub/mrpack-install 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/nothub/mrpack-install for upcoming vulnerabilities?

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