VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/MariusVanDerWijden/FuzzyVM: vulnerability history, versions and safety

github.com/MariusVanDerWijden/FuzzyVM 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 github.com/MariusVanDerWijden/FuzzyVM vulnerabilities

Vulert verdict on github.com/MariusVanDerWijden/FuzzyVM v0.0.0-20260727100435-c8f260e09738 i

Updated on 23 Oct 2026

Good news: v0.0.0-20260727100435-c8f260e09738, the version you would install today, has no known vulnerabilities.

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release v0.0.0-20260727100435-c8f260e09738 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 107 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 months ago i
  • Licence LGPL-2.1 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/MariusVanDerWijden/FuzzyVM, 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.0.0-20260727100435-c8f260e09738 27 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260724181750-ee5ceff9e821 24 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260715152058-90ca93c01ed1 15 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260714104741-3165253cbf4c 14 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260713151021-e30b412ba3a8 13 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260713150220-79827a85d20f 13 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260713142446-9c44a4942dfa 13 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260713112244-961670b5070b 13 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260709163116-8e58a05d337b 09 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260709160146-b334630e4fa7 09 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260709143901-1fa48df07e37 09 Jul 2026 none LGPL-2.1 — Details →
v0.0.0-20260630093212-940f48792a23 30 Jun 2026 none LGPL-2.1 — Details →
v0.0.0-20250703075614-d41fac3ca728 03 Jul 2025 none LGPL-2.1 — Details →
v0.0.0-20250605165815-58523f4fb4b1 05 Jun 2025 none LGPL-2.1 — Details →
v0.0.0-20250605131002-9939d55bd019 05 Jun 2025 none LGPL-2.1 — Details →
v0.0.0-20250603074746-d68662088506 03 Jun 2025 none LGPL-2.1 — Details →
v0.0.0-20250602123041-617fc5facb94 02 Jun 2025 none LGPL-2.1 — Details →
v0.0.0-20250528215329-14f7c0a4c1ca 28 May 2025 none LGPL-2.1 — Details →
v0.0.0-20250528214748-cc30d5107e56 28 May 2025 none LGPL-2.1 — Details →
v0.0.0-20250528211707-356f49791f2d 28 May 2025 none LGPL-2.1 — Details →
v0.0.0-20250528173357-617f77d14cb6 28 May 2025 none LGPL-2.1 — Details →
v0.0.0-20250306104318-61b96bc58ebc 06 Mar 2025 none LGPL-2.1 — Details →
v0.0.0-20250228190626-b582843c9dbe 28 Feb 2025 none LGPL-2.1 — Details →
v0.0.0-20250228184921-8e6892b683cb 28 Feb 2025 none LGPL-2.1 — Details →
v0.0.0-20240516070431-7828990cad7d 16 May 2024 none LGPL-2.1 — Details →
v0.0.0-20240516062919-621abf889fbb 16 May 2024 none LGPL-2.1 — Details →
v0.0.0-20240209103030-ec53fa766bf8 09 Feb 2024 none LGPL-2.1 — Details →
v0.0.0-20231208074501-0dce72108397 08 Dec 2023 none LGPL-2.1 — Details →
v0.0.0-20231208072100-9f36b6e85a76 08 Dec 2023 none LGPL-2.1 — Details →
v0.0.0-20231208064738-97c07018aa79 08 Dec 2023 none LGPL-2.1 — Details →
v0.0.0-20230606141057-24202385e744 06 Jun 2023 none LGPL-2.1 — Details →
v0.0.0-20230329161016-f7146b6f1dca 29 Mar 2023 none LGPL-2.1 — Details →
v0.0.0-20230329111514-571d68b84872 29 Mar 2023 none LGPL-2.1 — Details →
v0.0.0-20230329103937-cf9cfeb842de 29 Mar 2023 none LGPL-2.1 — Details →
v0.0.0-20230119161314-718c17cd7d6a 19 Jan 2023 none LGPL-2.1 — Details →
v0.0.0-20221202121132-bd37e8fb1d0d 02 Dec 2022 none LGPL-2.1 — Details →
v0.0.0-20220901111237-4348e62e228d 01 Sep 2022 none LGPL-2.1 — Details →
v0.0.0-20220304110512-764253afa8c2 04 Mar 2022 none LGPL-2.1 — Details →
v0.0.0-20220105083840-0d38b531cd4b 05 Jan 2022 none LGPL-2.1 — Details →
v0.0.0-20210904205340-da82a0d3e27a 04 Sep 2021 none LGPL-2.1 — Details →
v0.0.0-20210610151801-ba282cb82457 10 Jun 2021 none LGPL-2.1 — Details →
v0.0.0-20210602092503-80e8bb45c279 02 Jun 2021 none LGPL-2.1 — Details →
v0.0.0-20210531141435-79271fe730b9 31 May 2021 none LGPL-2.1 — Details →
v0.0.0-20210428104145-c6788db9a2eb 28 Apr 2021 none LGPL-2.1 — Details →
v0.0.0-20210409152000-6f7f8eaec461 09 Apr 2021 none LGPL-2.1 — Details →
v0.0.0-20201005184945-365e5833f278 05 Oct 2020 none LGPL-2.1 — Details →

All 46 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/MariusVanDerWijden/FuzzyVM

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/MariusVanDerWijden/FuzzyVM

Is github.com/MariusVanDerWijden/FuzzyVM safe to use?

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

Vulert scores github.com/MariusVanDerWijden/FuzzyVM 73/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/MariusVanDerWijden/FuzzyVM affected?

No. v0.0.0-20260727100435-c8f260e09738, 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/MariusVanDerWijden/FuzzyVM should I use?

v0.0.0-20260727100435-c8f260e09738 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/MariusVanDerWijden/FuzzyVM have?

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

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

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