Vulnerability Database · Go · Package report

github.com/bombsimon/wsl/v4: vulnerability history, versions and safety

github.com/bombsimon/wsl/v4 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/bombsimon/wsl/v4 v4.7.0 i

Updated on 23 Oct 2026

Good news: v4.7.0, the version you would install today, has no known vulnerabilities.

Package health score 65/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

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

  • Current release v4.7.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 365 i
  • OpenSSF scorecard 3/10 i
  • Last release 18 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/bombsimon/wsl/v4, 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
v4.7.0 03 Apr 2025 none MIT — Details →
v4.6.1-0.20250402220058-9ab31fcaf368 02 Apr 2025 none MIT — Details →
v4.5.1-0.20250224223841-da63f074c525 24 Feb 2025 none MIT — Details →
v4.6.0 24 Feb 2025 none MIT — Details →
v4.5.1-0.20250224223028-5eae4e364961 24 Feb 2025 none MIT — Details →
v4.5.1-0.20250106194016-ae575161f310 06 Jan 2025 none MIT — Details →
v4.4.2-0.20241227122327-b3eb50bfa311 27 Dec 2024 none MIT — Details →
v4.5.0 27 Dec 2024 none MIT — Details →
v4.4.2-0.20241217212937-52299dcd5c1c 17 Dec 2024 none MIT — Details →
v4.4.1 23 Jun 2024 none MIT — Details →
v4.4.1-0.20240623212340-c862f085c18f 23 Jun 2024 none MIT — Details →
v4.3.1-0.20240609151521-1fc4441e7e03 09 Jun 2024 none MIT — Details →
v4.4.0 09 Jun 2024 none MIT — Details →
v4.2.2-0.20240524204704-cf0fb6d3999c 24 May 2024 none MIT — Details →
v4.3.0 24 May 2024 none MIT — Details →
v4.2.2-0.20240325195707-115422b8a611 25 Mar 2024 none MIT — Details →
v4.2.1 08 Feb 2024 none MIT — Details →
v4.2.1-0.20240208202817-7c15727e1bca 08 Feb 2024 none MIT — Details →
v4.2.1-0.20240208200709-e2a5fce99b41 08 Feb 2024 none MIT — Details →
v4.1.1-0.20231128225146-956337b0c594 28 Nov 2023 none MIT — Details →
v4.2.0 28 Nov 2023 none MIT — Details →
v4.1.1-0.20231121192017-edc9d8c4c40f 21 Nov 2023 none MIT — Details →
v4.1.1-0.20231104114120-e5501b7a5a14 04 Nov 2023 none MIT — Details →
v4.0.1-0.20230616220358-4740984d9e36 16 Jun 2023 none MIT — Details →
v4.1.0 16 Jun 2023 none MIT — Details →
v4.0.1-0.20230608200827-64698e342f76 08 Jun 2023 none MIT — Details →
v4.0.1-0.20230528151643-09f4c06378eb 28 May 2023 none MIT — Details →
v4.0.1-0.20230420184250-c13b294135a3 20 Apr 2023 none MIT — Details →
v4.0.1-0.20230329055212-a91dc437ffc3 29 Mar 2023 none MIT — Details →
v4.0.1-0.20230327200441-b484e9dfcdf0 27 Mar 2023 none MIT — Details →
v4.0.1-0.20230317184423-ed6ecf5c97c4 17 Mar 2023 none MIT — Details →

All 31 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/bombsimon/wsl/v4

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/bombsimon/wsl/v4

Is github.com/bombsimon/wsl/v4 safe to use?

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

Vulert scores github.com/bombsimon/wsl/v4 65/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/bombsimon/wsl/v4 affected?

No. v4.7.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/bombsimon/wsl/v4 should I use?

v4.7.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/bombsimon/wsl/v4 have?

0 vulnerabilities are recorded for github.com/bombsimon/wsl/v4 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/bombsimon/wsl/v4 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/bombsimon/wsl/v4 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/bombsimon/wsl/v4 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/bombsimon/wsl/v4 for upcoming vulnerabilities?

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