VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

twitter-text: vulnerability history, versions and safety

twitter-text is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems 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 twitter-text vulnerabilities

Vulert verdict on twitter-text 3.1.0 i

Updated on 23 Oct 2026

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

Package health score 61/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 3.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 3,140 i
  • OpenSSF scorecard 2/10 i
  • Last release 78 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by RubyGems, 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 twitter-text, 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.1.0 31 Mar 2020 none Apache-2.0 — Details →
3.0.0 14 Oct 2018 none Apache-2.0 — Details →
2.1.0 21 Dec 2017 none Apache-2.0 — Details →
2.0.2 19 Dec 2017 none Apache-2.0 — Details →
2.0.1 18 Dec 2017 none Apache-2.0 — Details →
2.0.0 15 Dec 2017 none Apache-2.0 — Details →
1.14.7 03 Jul 2017 none Apache-2.0 — Details →
1.14.6 16 Jun 2017 none Apache-2.0 — Details →
1.14.5 11 Jan 2017 none Apache-2.0 — Details →
1.14.2 07 Dec 2016 none Apache-2.0 — Details →
1.14.1 04 Nov 2016 none Apache-2.0 — Details →
1.14.0 08 Jul 2016 none Apache-2.0 — Details →
1.13.4 03 Mar 2016 none Apache-2.0 — Details →
1.13.3 01 Feb 2016 none Apache-2.0 — Details →
1.13.0 31 Aug 2015 none Apache-2.0 — Details →
1.12.0 30 Apr 2015 none Apache-2.0 — Details →
1.11.0 27 Jan 2015 none Apache-2.0 — Details →
1.10.0 29 Oct 2014 none Apache-2.0 — Details →
1.9.2 24 Jul 2014 none Apache-2.0 — Details →
1.9.1 18 Jul 2014 none Apache-2.0 — Details →
1.9.0 18 Mar 2014 none Apache-2.0 — Details →
1.8.0 25 Feb 2014 none Apache-2.0 — Details →
1.7.0 13 Nov 2013 none Apache-2.0 — Details →
1.6.4 13 Nov 2013 none Apache-2.0 — Details →
1.6.3 16 Sep 2013 none Apache-2.0 — Details →
1.6.2 16 Sep 2013 none Apache-2.0 — Details →
1.6.1 11 Mar 2013 none — — Details →
1.6.0 01 Mar 2013 none — — Details →
1.5.0 18 Jun 2012 none — — Details →
1.4.17 23 Feb 2012 none — — Details →
1.4.16 07 Feb 2012 none — — Details →
1.4.15 02 Dec 2011 none — — Details →
1.4.14 01 Dec 2011 none — — Details →
1.4.13 02 Nov 2011 none — — Details →
1.4.12 04 Oct 2011 none — — Details →
1.4.11 26 Sep 2011 none — — Details →
1.4.10 20 Sep 2011 none — — Details →
1.4.9 05 Aug 2011 none — — Details →
1.4.8 13 Jul 2011 none — — Details →
1.4.7 08 Jul 2011 none — — Details →
1.4.6 22 Jun 2011 none — — Details →
1.4.5 22 Jun 2011 none — — Details →
1.3.4 21 Apr 2011 none — — Details →
1.3.3 21 Apr 2011 none — — Details →
1.3.2 20 Apr 2011 none — — Details →
1.4.2 19 Apr 2011 none — — Details →
1.4.1 19 Apr 2011 none — — Details →
1.3.1 06 Jan 2011 none — — Details →
1.3.0 06 Dec 2010 none — — Details →
1.2.5 18 Nov 2010 none — — Details →
1.2.4 03 Nov 2010 none — — Details →
1.2.3 01 Nov 2010 none — — Details →
1.2.2 08 Oct 2010 none — — Details →
1.2.1 05 Oct 2010 none — — Details →
1.2.0 05 Oct 2010 none — — Details →
1.1.8 23 Aug 2010 none — — Details →
1.1.7 19 Aug 2010 none — — Details →
1.1.6 10 Aug 2010 none — — Details →
1.1.5 23 Jul 2010 none — — Details →
1.1.4 09 Jul 2010 none — — Details →
1.1.2 11 May 2010 none — — Details →
1.1.1 28 Apr 2010 none — — Details →
1.0.4 11 Mar 2010 none — — Details →
1.0.3 06 Mar 2010 none — — Details →
1.0.2 05 Mar 2010 none — — Details →
1.0.1 08 Feb 2010 none — — Details →
1.0 27 Jan 2010 none — — Details →

All 67 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 twitter-text

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 twitter-text

Is twitter-text safe to use?

Vulert has no vulnerabilities on record for twitter-text in RubyGems 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 twitter-text's Vulert package health score?

Vulert scores twitter-text 61/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 twitter-text affected?

No. 3.1.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 twitter-text should I use?

3.1.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 twitter-text have?

0 vulnerabilities are recorded for twitter-text in the RubyGems 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 twitter-text vulnerabilities disclosed?

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

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