VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

rich-rst: vulnerability history, versions and safety

rich-rst is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI 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 rich-rst vulnerabilities

Vulert verdict on rich-rst 2.2.0 i

Updated on 23 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 2.2.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 9,144 packages i
  • Stars 21 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, 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 rich-rst, 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.2.0 27 Sep 2026 none MIT — Details →
2.1.0 05 Jul 2026 none MIT — Details →
2.0.3 04 Jul 2026 none MIT — Details →
2.0.2 25 Jun 2026 none MIT — Details →
2.0.1 16 May 2026 none MIT — Details →
2.0.0a9 11 May 2026 none MIT — Details →
2.0.0a8 10 May 2026 none MIT — Details →
2.0.0a7 05 Apr 2026 none MIT — Details →
2.0.0a6 04 Apr 2026 none MIT — Details →
2.0.0a4 03 Apr 2026 none MIT — Details →
2.0.0a3 03 Apr 2026 none MIT — Details →
2.0.0a2 03 Apr 2026 none MIT — Details →
2.0.0a1 03 Apr 2026 none MIT — Details →
1.3.2 14 Oct 2025 none MIT — Details →
1.3.1 30 Apr 2024 none MIT — Details →
1.3.0 25 Apr 2024 none MIT — Details →
1.2.0 26 Jan 2024 none MIT — Details →
1.1.7 08 Mar 2022 none MIT — Details →
1.1.6 08 Mar 2022 none MIT — Details →
1.1.5 10 Feb 2022 none MIT — Details →
1.1.4 10 Feb 2022 none MIT — Details →
1.1.3 08 Feb 2022 none MIT — Details →
1.1.2 07 Feb 2022 none MIT — Details →
1.1.0 07 Feb 2022 none MIT — Details →
1.0.1 06 Feb 2022 none MIT — Details →
1.0.0 06 Feb 2022 none MIT — Details →
1.0.0rc1 06 Feb 2022 none MIT — Details →
0.2.5 05 Feb 2022 none MIT — Details →
0.2.4 07 Nov 2021 none MIT — Details →
0.2.3 25 Oct 2021 none MIT — Details →
0.2.2 25 Oct 2021 none MIT — Details →
0.2.1 25 Oct 2021 none MIT — Details →
0.2.0 25 Oct 2021 none MIT — Details →
0.1.0 06 Sep 2021 none MIT — Details →

All 34 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 rich-rst

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 rich-rst

Is rich-rst safe to use?

Vulert has no vulnerabilities on record for rich-rst in PyPI 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 rich-rst's Vulert package health score?

Vulert scores rich-rst 75/100, which reads as in good shape. 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 rich-rst affected?

No. 2.2.0, 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 rich-rst should I use?

2.2.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 rich-rst have?

0 vulnerabilities are recorded for rich-rst in the PyPI 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 rich-rst vulnerabilities disclosed?

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

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