Is qcell safe to use?

Vulert records 2 vulnerabilities for qcell in crates.io: 0 critical, 1 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 qcell's Vulert package health score?

Vulert scores qcell 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 qcell affected?

No. 0.5.5, 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 qcell should I use?

0.5.5 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 qcell have?

2 vulnerabilities are recorded for qcell in the crates.io ecosystem: 0 critical, 1 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 qcell vulnerabilities disclosed?

0 vulnerabilities were recorded for qcell in the last 12 months, and the oldest entry in this database dates to 24 Jan 2022. 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 qcell 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 qcell for upcoming vulnerabilities?

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

Vulnerability Database · crates.io · Package report

qcell: vulnerability history, versions and safety

qcell is a package in the crates.io ecosystem. Vulert records 2 vulnerabilities for it across 8 releases, from Jan 2022 to Jun 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

2 vulnerabilities recorded H1 U1

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all qcell vulnerabilities

Vulert verdict on qcell 0.5.5 i

Updated on 23 Oct 2026

Good news: 0.5.5, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 65/100

Security Minor issues
Maintenance Maintaining
Popularity Niche
Community Inactive

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

Current release 0.5.5 — unaffected i
Vulnerabilities on record 2 over 1 year · 0 in the last year i
Latest disclosure 17 Jun 2022 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 13 packages i
Stars 392 i
OpenSSF scorecard 1/10 i
Last release 13 months ago i
Licence Apache-2.0 OR MIT i
Similar names vcell i

Version list, release dates, licence and dependants published by crates.io, refreshed 22 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for qcell, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
0.5.5	17 Sep 2025	none	Apache-2.0 OR MIT	—	Details →
0.5.4	13 Jul 2023	none	Apache-2.0 OR MIT	—	Details →
0.5.3	15 Jan 2023	none	Apache-2.0 OR MIT	—	Details →
0.5.2	11 Jun 2022	none	Apache-2.0 OR MIT	—	Details →
0.5.1	19 Apr 2022	none	Apache-2.0 OR MIT	—	Details →
0.5.0	23 Jan 2022	none	Apache-2.0 OR MIT	—	Details →
0.4.3	21 Sep 2021	none	Apache-2.0 OR MIT	—	Details →
0.4.2	20 Aug 2021	H1 U1	Apache-2.0 OR MIT	Yes	Details →
0.4.1	25 Jun 2020	H1 U1	Apache-2.0 OR MIT	Yes	Details →
0.4.0	24 Dec 2019	H1 U1	Apache-2.0 OR MIT	Yes	Details →
0.3.0	24 Jul 2019	H1 U1	Apache-2.0 OR MIT	Yes	Details →
0.2.0	21 Mar 2019	H1 U1	Apache-2.0 OR MIT	Yes	Details →
0.1.2	18 Mar 2019	H1 U1	Apache-2.0 OR MIT	Yes	Details →
0.1.1	07 Mar 2019	H1 U1	Apache-2.0 OR MIT	Yes	Details →
0.1.0	28 Feb 2019	H1 U1	Apache-2.0 OR MIT	Yes	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

2022 2

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for qcell

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2022-0007: qcell - Unsound Access to TCell or TLCell Memory	N/A unrated	0.4.3	24 Jan 2022
Unsound Access to TCell or TLCell Memory in qcell	N/A high	0.4.3	17 Jun 2022

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