Vulnerability Database · Go · Package report

github.com/migueleliasweb/go-github-mock: vulnerability history, versions and safety

github.com/migueleliasweb/go-github-mock 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.

Vulert verdict on github.com/migueleliasweb/go-github-mock v1.5.0 i

Updated on 23 Oct 2026

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

Package health score 66/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.5.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 140 i
  • OpenSSF scorecard 1/10 i
  • Last release 12 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/migueleliasweb/go-github-mock, 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.1-0.20251019225949-cd7e39800e7f 19 Oct 2025 none MIT — Details →
v1.5.0 19 Oct 2025 none MIT — Details →
v1.3.1-0.20251009220948-557ab231ee17 09 Oct 2025 none MIT — Details →
v1.4.0 26 Jun 2025 none MIT — Details →
v1.3.1-0.20250626115536-86f5db0c11b6 26 Jun 2025 none MIT — Details →
v1.3.0 04 May 2025 none MIT — Details →
v1.1.1-0.20250301114641-478be8dfecba 01 Mar 2025 none MIT — Details →
v1.2.0 01 Mar 2025 none MIT — Details →
v1.0.2-0.20241021124749-c9fc79552456 21 Oct 2024 none MIT — Details →
v1.1.0 21 Oct 2024 none MIT — Details →
v1.0.1 22 Aug 2024 none MIT — Details →
v1.0.1-0.20240822131301-65485f3c5c75 22 Aug 2024 none MIT — Details →
v0.0.24-0.20240506121511-12eaf763b1f7 06 May 2024 none MIT — Details →
v1.0.0 06 May 2024 none MIT — Details →
v0.0.23 23 Feb 2024 none MIT — Details →
v0.0.23-0.20240223102112-35555fd48607 23 Feb 2024 none MIT — Details →
v0.0.23-0.20240214235154-c59fff968475 14 Feb 2024 none MIT — Details →
v0.0.21-0.20231103111513-be5e2c518c3d 03 Nov 2023 none MIT — Details →
v0.0.22 03 Nov 2023 none MIT — Details →
v0.0.21-0.20231027231029-ebbb9387871a 27 Oct 2023 none MIT — Details →
v0.0.21 27 Oct 2023 none MIT — Details →
v0.0.20 22 Sep 2023 none MIT — Details →
v0.0.20-0.20230922095141-1784f27b54c9 22 Sep 2023 none MIT — Details →
v0.0.20-0.20230622121320-c482c22b0174 22 Jun 2023 none MIT — Details →
v0.0.19 22 Jun 2023 none MIT — Details →
v0.0.19-0.20230622120510-68c499fe2c8c 22 Jun 2023 none MIT — Details →
v0.0.19-0.20230621013836-3cfe4e552070 21 Jun 2023 none MIT — Details →
v0.0.19-0.20230615141546-c491f605700b 15 Jun 2023 none MIT — Details →
v0.0.18 19 May 2023 none MIT — Details →
v0.0.17 19 Apr 2023 none MIT — Details →
v0.0.16 28 Jan 2023 none MIT — Details →
v0.0.15 26 Jan 2023 none MIT — Details →
v0.0.14 22 Jan 2023 none MIT — Details →
v0.0.0-20221015051240-e08e47f7518d 15 Oct 2022 none MIT — Details →
v0.0.13 15 Oct 2022 none MIT — Details →
v0.0.13-0.20221013121726-35a3ffad7fb3 13 Oct 2022 none MIT — Details →
v0.0.12 06 Sep 2022 none MIT — Details →
v0.0.11-0.20220718121952-1984a6b97c0c 18 Jul 2022 none MIT — Details →
v0.0.11-alpha 18 Jul 2022 none MIT — Details →
v0.0.10 04 Jul 2022 none MIT — Details →
v0.0.9-0.20220416020236-2d7c3cb4e244 16 Apr 2022 none MIT — Details →
v0.0.9-beta 16 Apr 2022 none MIT — Details →
v0.0.9-0.20220406115827-1cba4e2d2ed5 06 Apr 2022 none MIT — Details →
v0.0.9-0.20220326010837-9e79866007cb 26 Mar 2022 none MIT — Details →
v0.0.8 23 Mar 2022 none MIT — Details →
v0.0.7 20 Feb 2022 none MIT — Details →
v0.0.6 07 Jan 2022 none MIT — Details →
v0.0.6-0.20211210084309-6d9a5e264c98 10 Dec 2021 none MIT — Details →
v0.0.5 02 Oct 2021 none MIT — Details →
v0.0.5-0.20211001125456-c8331fe00b74 01 Oct 2021 none MIT — Details →
v0.0.0-20210827152142-25ab056598ec 27 Aug 2021 none MIT — Details →
v0.0.4 27 Aug 2021 none MIT — Details →
v0.0.4-0.20210827143837-b3380a1f28fe 27 Aug 2021 none MIT — Details →
v0.0.3 27 Aug 2021 none MIT — Details →
v0.0.2 12 Aug 2021 none MIT — Details →
v0.0.2-0.20210810125849-1e92357b7426 10 Aug 2021 none MIT — Details →
v0.0.1 28 Jul 2021 none MIT — Details →
v0.0.0-20210727135000-c16a709bc1e0 27 Jul 2021 none MIT — Details →

All 58 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/migueleliasweb/go-github-mock

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/migueleliasweb/go-github-mock

Is github.com/migueleliasweb/go-github-mock safe to use?

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

Vulert scores github.com/migueleliasweb/go-github-mock 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/migueleliasweb/go-github-mock affected?

No. v1.5.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/migueleliasweb/go-github-mock should I use?

v1.5.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/migueleliasweb/go-github-mock have?

0 vulnerabilities are recorded for github.com/migueleliasweb/go-github-mock 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/migueleliasweb/go-github-mock vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/migueleliasweb/go-github-mock 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/migueleliasweb/go-github-mock 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/migueleliasweb/go-github-mock for upcoming vulnerabilities?

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