VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

lzw: vulnerability history, versions and safety

lzw is a package in the crates.io ecosystem. Vulert records 1 vulnerability for it across 9 releases, first recorded in Feb 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded U1
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 lzw vulnerabilities

Vulert verdict on lzw 0.10.0 i

Updated on 23 Oct 2026

Action needed: 0.10.0 has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 56/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 0.10.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 10 Feb 2020 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 598 packages i
  • Stars 8 i
  • OpenSSF scorecard 1/10 i
  • Last release 127 months ago i
  • Licence Apache-2.0 OR MIT i
  • Similar names lz4 i

Version list, release dates, licence and dependants published by crates.io, 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 lzw, 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
0.10.0 28 Feb 2016 U1 Apache-2.0 OR MIT Yes Details →
0.9.0 07 Jun 2015 U1 MIT Yes Details →
0.8.0 05 Jun 2015 U1 Apache-2.0 OR MIT Yes Details →
0.7.0 01 May 2015 U1 MIT Yes Details →
0.5.0 24 Apr 2015 U1 MIT Yes Details →
0.4.0 22 Apr 2015 U1 MIT Yes Details →
0.3.0 21 Apr 2015 U1 MIT Yes Details →
0.2.0 03 Apr 2015 U1 MIT Yes Details →
0.1.0 01 Apr 2015 U1 MIT Yes Details →

All 9 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for lzw

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Unmaintained lzw crate in Rust N/A unrated 0.10.1-0 10 Feb 2020

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 lzw

Is lzw safe to use?

Vulert records 1 vulnerabilities for lzw in crates.io: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is lzw's Vulert package health score?

Vulert scores lzw 56/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 lzw affected?

Yes. 0.10.0, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of lzw should I use?

0.10.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 lzw have?

1 vulnerability is recorded for lzw in the crates.io ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new lzw vulnerabilities disclosed?

0 vulnerabilities were recorded for lzw in the last 12 months, and the oldest entry in this database dates to 10 Feb 2020. 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 lzw 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 lzw for upcoming vulnerabilities?

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