VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

quickersort: vulnerability history, versions and safety

quickersort is a package in the crates.io ecosystem. Vulert records 1 vulnerability for it across 9 releases, first recorded in Jun 2018. 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 quickersort vulnerabilities

Vulert verdict on quickersort 3.0.1 i

Updated on 23 Oct 2026

Action needed: 3.0.1 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 37/100
  • Security Minor issues
  • Maintenance Deprecated
  • Popularity Little adoption
  • Community Inactive

The registry marks the latest release as deprecated, which caps this score.

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 3.0.1 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 30 Jun 2018 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 17 i
  • OpenSSF scorecard 1/10 i
  • Last release 104 months ago i
  • Licence Apache-2.0 OR MIT 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 quickersort, 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
3.0.1 30 Jan 2018 U1 Apache-2.0 OR MIT Yes Details →
3.0.0 30 May 2017 U1 Apache-2.0 OR MIT Yes Details →
2.2.0 20 Dec 2016 U1 Apache-2.0 OR MIT Yes Details →
2.1.1 14 Oct 2016 U1 Apache-2.0 OR MIT Yes Details →
2.1.0 18 Aug 2016 U1 Apache-2.0 OR MIT Yes Details →
2.0.1 02 May 2016 U1 Apache-2.0 OR MIT Yes Details →
2.0.0 23 Apr 2016 U1 Apache-2.0 OR MIT Yes Details →
1.0.1 21 Jan 2016 U1 Apache-2.0 OR MIT Yes Details →
1.0.0 30 Jul 2015 U1 Apache-2.0 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

  • 2018 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 quickersort

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Deprecated and Unmaintained quickersort Package N/A unrated 3.0.2-0 30 Jun 2018

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 quickersort

Is quickersort safe to use?

Vulert records 1 vulnerabilities for quickersort 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 quickersort's Vulert package health score?

Vulert scores quickersort 37/100, which reads as risky. 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). The registry marks the latest release as deprecated, which caps this score.

Is the latest version of quickersort affected?

Yes. 3.0.1, 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 quickersort should I use?

3.0.1 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 quickersort have?

1 vulnerability is recorded for quickersort 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 quickersort vulnerabilities disclosed?

0 vulnerabilities were recorded for quickersort in the last 12 months, and the oldest entry in this database dates to 30 Jun 2018. 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 quickersort 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 quickersort for upcoming vulnerabilities?

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