Vulnerability Database · crates.io · Package report

subtle: vulnerability history, versions and safety

subtle is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the crates.io 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 subtle 2.6.1 i

Updated on 23 Oct 2026

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

Package health score 63/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release 2.6.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 5,031 packages i
  • Stars 312 i
  • OpenSSF scorecard 3/10 i
  • Last release 27 months ago i
  • Licence BSD-3-Clause 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 subtle, 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
2.6.1 24 Jun 2024 none BSD-3-Clause — Details →
2.6.0 19 Jun 2024 none BSD-3-Clause — Details →
2.5.0 28 Feb 2023 none BSD-3-Clause — Details →
2.4.1 13 Jul 2021 none BSD-3-Clause — Details →
2.4.0 17 Dec 2020 none BSD-3-Clause — Details →
2.3.0 08 Sep 2020 none BSD-3-Clause — Details →
2.2.3 29 May 2020 none BSD-3-Clause — Details →
2.2.2 27 Nov 2019 none BSD-3-Clause — Details →
2.2.1 28 Sep 2019 none BSD-3-Clause — Details →
2.2.0 27 Sep 2019 none BSD-3-Clause — Details →
2.1.1 31 Jul 2019 none BSD-3-Clause — Details →
2.1.0 29 Apr 2019 none BSD-3-Clause — Details →
2.0.0 13 Dec 2018 none BSD-3-Clause — Details →
2.0.0-pre.0 05 Nov 2018 none BSD-3-Clause — Details →
1.0.0 25 Sep 2018 none BSD-3-Clause — Details →
0.9.0 05 Sep 2018 none BSD-3-Clause — Details →
0.8.0 05 Sep 2018 none BSD-3-Clause — Details →
0.7.1 04 Sep 2018 none BSD-3-Clause — Details →
0.7.0 04 Jul 2018 none BSD-3-Clause — Details →
0.6.3 20 Jun 2018 none BSD-3-Clause — Details →
0.6.2 12 Apr 2018 none BSD-3-Clause — Details →
0.6.1 12 Apr 2018 none BSD-3-Clause — Details →
0.6.0 19 Mar 2018 none BSD-3-Clause — Details →
0.5.1 30 Jan 2018 none BSD-3-Clause — Details →
0.5.0 20 Jan 2018 none BSD-3-Clause — Details →
0.4.0 20 Jan 2018 none CC0-1.0 — Details →
0.3.0 05 Oct 2017 none CC0-1.0 — Details →
0.2.0 31 Jul 2017 none CC0-1.0 — Details →
0.1.0 31 May 2017 none CC0-1.0 — Details →

All 29 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 subtle

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 subtle

Is subtle safe to use?

Vulert has no vulnerabilities on record for subtle in crates.io 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 subtle's Vulert package health score?

Vulert scores subtle 63/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 subtle affected?

No. 2.6.1, 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 subtle should I use?

2.6.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 subtle have?

0 vulnerabilities are recorded for subtle in the crates.io 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 subtle vulnerabilities disclosed?

0 vulnerabilities were recorded for subtle 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 subtle 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 subtle for upcoming vulnerabilities?

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