Vulnerability Database · Go · Package report
github.com/extism/go-pdk/wasi-reactor: vulnerability history, versions and safety
github.com/extism/go-pdk/wasi-reactor is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
See all github.com/extism/go-pdk/wasi-reactor vulnerabilities
Vulert verdict on github.com/extism/go-pdk/wasi-reactor v0.0.0-20260122165646-35abd9e2ba55 i
Updated on 23 Oct 2026
Good news: v0.0.0-20260122165646-35abd9e2ba55, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v0.0.0-20260122165646-35abd9e2ba55 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260122165646-35abd9e2ba55 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.0.0-20260122165646-35abd9e2ba55 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 93 i
- OpenSSF scorecard 2/10 i
- Last release 9 months ago i
- Licence BSD-3-Clause 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/extism/go-pdk/wasi-reactor, 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.
- v0.0.0-20260122165646-35abd9e2ba55 22 Jan 2026
- v0.0.0-20251229151220-1d9688e108bf 29 Dec 2025
- v0.0.0-20251220054449-1287e269ab4d 20 Dec 2025
- v0.0.0-20250318023836-12d6f9af953a 18 Mar 2025
- v0.0.0-20250205222910-eea8e06b98e9 05 Feb 2025
- v0.0.0-20250124183739-ff1c4f6d86f1 24 Jan 2025
- v0.0.0-20241120064915-15022184ecbe 20 Nov 2024
- v0.0.0-20241104144903-71c0263a621b 04 Nov 2024
- v0.0.0-20241024174837-55cb61278782 24 Oct 2024
- v0.0.0-20241015192902-cf652fce1d39 15 Oct 2024
- v0.0.0-20240822224546-49215e07ce75 22 Aug 2024
- v0.0.0-20240804170849-7cb3d48ce7cc 04 Aug 2024
- v0.0.0-20240722175701-3f3217105fb8 22 Jul 2024
- v0.0.0-20240717191542-7180e57f1b61 17 Jul 2024
- v0.0.0-20240715223242-fe9942ac0bb5 15 Jul 2024
- v0.0.0-20240713012319-855c34fe3d74 13 Jul 2024
- v0.0.0-20240618165300-de6b7b8bb649 18 Jun 2024
- v0.0.0-20240617204011-e565f18cf414 17 Jun 2024
- v0.0.0-20240408161339-095ac11ddc4e 08 Apr 2024
- v0.0.0-20240318204741-8d2782c6ff52 18 Mar 2024
- v0.0.0-20240202061512-fae85da4456d 02 Feb 2024
- v0.0.0-20240130003926-6e7ff40e17b8 30 Jan 2024
- v0.0.0-20240118192922-d48f368ae145 18 Jan 2024
All 23 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/extism/go-pdk/wasi-reactor
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
Questions
About github.com/extism/go-pdk/wasi-reactor
Is github.com/extism/go-pdk/wasi-reactor safe to use?
Vulert has no vulnerabilities on record for github.com/extism/go-pdk/wasi-reactor 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/extism/go-pdk/wasi-reactor's Vulert package health score?
Vulert scores github.com/extism/go-pdk/wasi-reactor 68/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/extism/go-pdk/wasi-reactor affected?
No. v0.0.0-20260122165646-35abd9e2ba55, 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/extism/go-pdk/wasi-reactor should I use?
v0.0.0-20260122165646-35abd9e2ba55 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/extism/go-pdk/wasi-reactor have?
0 vulnerabilities are recorded for github.com/extism/go-pdk/wasi-reactor 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/extism/go-pdk/wasi-reactor vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/extism/go-pdk/wasi-reactor 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/extism/go-pdk/wasi-reactor 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/extism/go-pdk/wasi-reactor for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/extism/go-pdk/wasi-reactor version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.