VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/sorairolake/lzip-go: vulnerability history, versions and safety

github.com/sorairolake/lzip-go 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/sorairolake/lzip-go vulnerabilities

Vulert verdict on github.com/sorairolake/lzip-go v0.3.8 i

Updated on 23 Oct 2026

Good news: v0.3.8, the version you would install today, has no known vulnerabilities.

Package health score 58/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.3.8 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 9 i
  • OpenSSF scorecard 3/10 i
  • Last release 14 months ago 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/sorairolake/lzip-go, 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-20260515155903-48aa076d321d 15 May 2026 none Apache-2.0 — Details →
v0.3.8 22 Aug 2025 none Apache-2.0 — Details →
v0.3.7 23 Mar 2025 none Apache-2.0 — Details →
v0.3.6 23 Mar 2025 none Apache-2.0 — Details →
v0.0.0-20241205013510-ff629183bd1d 05 Dec 2024 none Apache-2.0 — Details →
v0.0.0-20241116232703-b51d9f53e7aa 16 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241111131250-104130ce3af4 11 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241108065042-c4c6e6c79aa3 08 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241030162521-8071b925dcc1 30 Oct 2024 none Apache-2.0 — Details →
v0.0.0-20240930213903-761ca3c6ac53 30 Sep 2024 none Apache-2.0 — Details →
v0.0.0-20240918094910-9b072bcbcb4b 18 Sep 2024 none Apache-2.0 — Details →
v0.0.0-20240913062447-db31f70db615 13 Sep 2024 none Apache-2.0 — Details →
v0.0.0-20240908103335-462b221b63f2 08 Sep 2024 none Apache-2.0 — Details →
v0.0.0-20240804090753-08528e2c802f 04 Aug 2024 none Apache-2.0 — Details →
v0.3.5 04 Aug 2024 none Apache-2.0 — Details →
v0.0.0-20240802101222-cb16d5bc955a 02 Aug 2024 none Apache-2.0 — Details →
v0.0.0-20240801080634-8587af0dacba 01 Aug 2024 none Apache-2.0 — Details →
v0.0.0-20240727023701-6af22a4c4407 27 Jul 2024 none Apache-2.0 — Details →
v0.0.0-20240710170714-15cfc7c8ad38 10 Jul 2024 none Apache-2.0 — Details →
v0.0.0-20240704135730-7d4950542859 04 Jul 2024 none Apache-2.0 — Details →
v0.0.0-20240513232108-f68ccbf9fe49 13 May 2024 none Apache-2.0 — Details →
v0.0.0-20240503073911-48b3d0de0d6d 03 May 2024 none Apache-2.0 — Details →
v0.3.4 02 May 2024 none Apache-2.0 — Details →
v0.0.0-20240501102759-484cd23e79fc 01 May 2024 none Apache-2.0 — Details →
v0.0.0-20240427012251-d99241003cbb 27 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240421065209-2337d1733c83 21 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240420104434-4aac58044b3e 20 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240416034621-c721660bc20c 16 Apr 2024 none Apache-2.0 — Details →
v0.3.3 16 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240414004905-791fef518486 14 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240410131550-92397eab1eed 10 Apr 2024 none Apache-2.0 — Details →
v0.3.2 10 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240408121332-c406d8f4a57c 08 Apr 2024 none Apache-2.0 — Details →
v0.3.1 08 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240408102213-e6c0637eea24 08 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240408051218-83a5d3e7aadf 08 Apr 2024 none Apache-2.0 — Details →
v0.3.0 07 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240406105900-64ae7f6a6080 06 Apr 2024 none Apache-2.0 — Details →
v0.2.0 05 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240404232348-a4c7a67c6f22 04 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240404154956-3cd55d89271b 04 Apr 2024 none Apache-2.0 — Details →
v0.1.0 04 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20240402092006-1e4d5a967ef5 02 Apr 2024 none Apache-2.0 — Details →

All 43 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/sorairolake/lzip-go

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/sorairolake/lzip-go

Is github.com/sorairolake/lzip-go safe to use?

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

Vulert scores github.com/sorairolake/lzip-go 58/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/sorairolake/lzip-go affected?

No. v0.3.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.

Which version of github.com/sorairolake/lzip-go should I use?

v0.3.8 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/sorairolake/lzip-go have?

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

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

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