VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

text_helpers: vulnerability history, versions and safety

text_helpers is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 2 releases, first recorded in Dec 2022. 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 M1
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 text_helpers vulnerabilities

Vulert verdict on text_helpers 1.2.0 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 1.2.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 22 Dec 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Last release 57 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, 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.

01 Versions

Which versions are affected

Every version Vulert tracks for text_helpers, 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
1.2.0 05 Jan 2022 none MIT — Details →
1.1.1 03 Feb 2021 M1 MIT Yes Details →
1.1.0 09 Dec 2020 M1 MIT Yes Details →
1.0.1 03 Dec 2020 none MIT — Details →
1.0.0 27 Mar 2020 none MIT — Details →
0.7.2 06 Jul 2019 none MIT — Details →
0.7.1 06 Jul 2019 none MIT — Details →
0.7.0 06 May 2016 none MIT — Details →
0.6.1 01 Oct 2015 none MIT — Details →
0.6.0 11 Jun 2015 none MIT — Details →
0.5.3 25 Feb 2015 none MIT — Details →
0.5.2 03 Feb 2015 none MIT — Details →
0.5.1 24 Jan 2015 none MIT — Details →
0.5.0 23 Jan 2015 none MIT — Details →
0.4.2 07 Oct 2014 none MIT — Details →
0.4.1 06 Oct 2014 none MIT — Details →
0.4.0 04 Oct 2014 none MIT — Details →
0.3.2 21 Mar 2014 none MIT — Details →
0.3.1 20 Mar 2014 none MIT — Details →
0.2.2 10 Mar 2014 none MIT — Details →
0.2.1 26 Dec 2013 none MIT — Details →
0.2.0 10 Dec 2013 none MIT — Details →
0.1.8 03 Dec 2013 none MIT — Details →
0.1.7 03 Dec 2013 none MIT — Details →
0.1.6 03 Dec 2013 none MIT — Details →
0.1.5 14 Nov 2013 none MIT — Details →
0.1.3 11 Nov 2013 none MIT — Details →
0.1.2 01 Nov 2013 none MIT — Details →
0.1.1 30 Oct 2013 none — — Details →
0.1.0 15 Oct 2013 none — — Details →

All 30 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 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 text_helpers

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-36624: Vulnerability in text_helpers package 6.1 medium 1.2.0 22 Dec 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

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 text_helpers

Is text_helpers safe to use?

Vulert records 1 vulnerabilities for text_helpers in RubyGems: 0 critical, 0 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is text_helpers's Vulert package health score?

Vulert scores text_helpers 80/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 text_helpers affected?

No. 1.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 text_helpers should I use?

1.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 text_helpers have?

1 vulnerability is recorded for text_helpers in the RubyGems ecosystem: 0 critical, 0 high, 1 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 text_helpers vulnerabilities disclosed?

0 vulnerabilities were recorded for text_helpers in the last 12 months, and the oldest entry in this database dates to 22 Dec 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 text_helpers 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 text_helpers for upcoming vulnerabilities?

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