Vulnerability Database · Go · Package report

github.com/bytedance/mockey: vulnerability history, versions and safety

github.com/bytedance/mockey 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/bytedance/mockey v1.4.8 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release v1.4.8 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 908 i
  • OpenSSF scorecard 3/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/bytedance/mockey, 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.8 16 Oct 2026 none Apache-2.0 — Details →
v1.4.7 16 Sep 2026 none Apache-2.0 — Details →
v1.4.6 17 Apr 2026 none Apache-2.0 — Details →
v1.4.5 07 Mar 2026 none Apache-2.0 — Details →
v1.4.5-0.20260122025021-8e1ce0cd0212 22 Jan 2026 none Apache-2.0 — Details →
v1.4.4 20 Jan 2026 none Apache-2.0 — Details →
v1.4.3 19 Jan 2026 none Apache-2.0 — Details →
v1.4.2 13 Jan 2026 none Apache-2.0 — Details →
v1.4.1 08 Jan 2026 none Apache-2.0 — Details →
v1.4.0 19 Dec 2025 none Apache-2.0 — Details →
v1.4.0-beta.0.20251219045833-9d0987cd5ff3 19 Dec 2025 none Apache-2.0 — Details →
v1.4.0-beta 18 Dec 2025 none Apache-2.0 — Details →
v1.3.2 01 Dec 2025 none Apache-2.0 — Details →
v1.3.1 28 Nov 2025 none Apache-2.0 — Details →
v1.3.0 25 Nov 2025 none Apache-2.0 — Details →
v1.3.0-beta 20 Nov 2025 none Apache-2.0 — Details →
v1.3.0-alpha 19 Nov 2025 none Apache-2.0 — Details →
v1.2.17 11 Nov 2025 none Apache-2.0 — Details →
v1.2.17-0.20251107082459-c7fc28dd83b0 07 Nov 2025 none Apache-2.0 — Details →
v1.2.17-0.20251106112212-2b9815978151 06 Nov 2025 none Apache-2.0 — Details →
v1.2.16 03 Nov 2025 none Apache-2.0 — Details →
v1.2.15 17 Oct 2025 none Apache-2.0 — Details →
v0.0.0-20250219093958-7b017bb077e8 19 Feb 2025 none Apache-2.0 — Details →
v1.2.15-0.20250219093958-7b017bb077e8 19 Feb 2025 none Apache-2.0 — Details →
v1.2.14 21 Jan 2025 none Apache-2.0 — Details →
v1.2.13 16 Oct 2024 none Apache-2.0 — Details →
v1.2.13-0.20241016084407-fd3aa18e5f32 16 Oct 2024 none Apache-2.0 — Details →
v1.2.13-0.20240919112736-9190821a18cb 19 Sep 2024 none Apache-2.0 — Details →
v1.2.12 03 Sep 2024 none Apache-2.0 — Details →
v1.2.12-0.20240903063523-07cb384c4d3b 03 Sep 2024 none Apache-2.0 — Details →
v1.2.11 20 Aug 2024 none Apache-2.0 — Details →
v1.2.11-0.20240820113304-69f3314a97c9 20 Aug 2024 none Apache-2.0 — Details →
v1.2.11-0.20240815091636-567d66ff56b0 15 Aug 2024 none Apache-2.0 — Details →
v1.2.10 17 Jan 2024 none Apache-2.0 — Details →
v1.2.10-0.20240117025515-a60edcc5b06d 17 Jan 2024 none Apache-2.0 — Details →
v1.2.9 30 Oct 2023 none Apache-2.0 — Details →
v1.2.9-0.20231030024018-1df46d9d1f3c 30 Oct 2023 none Apache-2.0 — Details →
v1.2.9-0.20231024024657-1c098ecc3aa7 24 Oct 2023 none Apache-2.0 — Details →
v1.2.8 23 Oct 2023 none Apache-2.0 — Details →
v1.2.7 19 Oct 2023 none Apache-2.0 — Details →
v1.2.7-0.20231019062331-01cec8fad985 19 Oct 2023 none Apache-2.0 — Details →
v1.2.7-0.20231017050409-544448c22087 17 Oct 2023 none Apache-2.0 — Details →
v1.2.7-0.20231009070019-e4d8a3b60d0a 09 Oct 2023 none Apache-2.0 — Details →
v1.2.6 18 Sep 2023 none Apache-2.0 — Details →
v1.2.6-0.20230918081339-7eec1630c64b 18 Sep 2023 none Apache-2.0 — Details →
v1.2.5 04 Sep 2023 none Apache-2.0 — Details →
v1.2.5-alpha.3.0.20230904031129-15c9b8268c1d 04 Sep 2023 none Apache-2.0 — Details →
v1.2.5-alpha.2.0.20230814032537-3ffd17296547 14 Aug 2023 none Apache-2.0 — Details →
v1.2.5-alpha.3 14 Aug 2023 none Apache-2.0 — Details →
v1.2.5-alpha.0.20230803114008-784cc5ef04f5 03 Aug 2023 none Apache-2.0 — Details →
v1.2.5-alpha.2 03 Aug 2023 none Apache-2.0 — Details →
v1.2.5-0.20230728064516-e4ac070bfece 28 Jul 2023 none Apache-2.0 — Details →
v1.2.5-alpha 28 Jul 2023 none Apache-2.0 — Details →
v1.2.5-0.20230605045737-2c5cfce4721d 05 Jun 2023 none Apache-2.0 — Details →
v1.2.4 30 May 2023 none Apache-2.0 — Details →
v1.2.4-0.20230530040053-d9d603efdd96 30 May 2023 none Apache-2.0 — Details →
v1.2.3 22 May 2023 none Apache-2.0 — Details →
v1.2.2 24 Apr 2023 none Apache-2.0 — Details →
v1.2.2-0.20230424072024-e48d0003db7a 24 Apr 2023 none Apache-2.0 — Details →
v1.2.1 01 Mar 2023 none Apache-2.0 — Details →
v1.2.1-0.20230301033940-253cbce59f13 01 Mar 2023 none Apache-2.0 — Details →
v1.1.2-0.20230228020300-5e2623fb27f8 28 Feb 2023 none Apache-2.0 — Details →
v1.2.0 28 Feb 2023 none Apache-2.0 — Details →
v1.1.1 18 Jan 2023 none Apache-2.0 — Details →
v1.0.1-0.20230105113932-2344cac42c43 05 Jan 2023 none Apache-2.0 — Details →
v1.1.0 05 Jan 2023 none Apache-2.0 — Details →
v1.0.1-0.20230104123943-8267634b513d 04 Jan 2023 none Apache-2.0 — Details →
v1.0.1-0.20221229081644-e8a79c6b3dc3 29 Dec 2022 none Apache-2.0 — Details →
v1.0.0 29 Dec 2022 none Apache-2.0 — Details →
v1.0.0-rc.0.0.20221028095600-fa6618d5a234 28 Oct 2022 none Apache-2.0 — Details →
v1.0.0-rc.0.0.20220928135207-73fa87957dbf 28 Sep 2022 none Apache-2.0 — Details →
v0.0.0-20220927130630-b594b3563c7c 27 Sep 2022 none Apache-2.0 — Details →
v1.0.0-beta 27 Sep 2022 none Apache-2.0 — Details →
v1.0.0-rc.0 27 Sep 2022 none Apache-2.0 — Details →

All 74 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/bytedance/mockey

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/bytedance/mockey

Is github.com/bytedance/mockey safe to use?

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

Vulert scores github.com/bytedance/mockey 78/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/bytedance/mockey affected?

No. v1.4.8, 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.

How many vulnerabilities does github.com/bytedance/mockey have?

0 vulnerabilities are recorded for github.com/bytedance/mockey 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/bytedance/mockey vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/bytedance/mockey 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/bytedance/mockey 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/bytedance/mockey for upcoming vulnerabilities?

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