Is twitter-stream safe to use?

Vulert records 1 vulnerabilities for twitter-stream in RubyGems: 0 critical, 0 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is twitter-stream's Vulert package health score?

Vulert scores twitter-stream 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of twitter-stream affected?

Yes. 0.1.16, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of twitter-stream should I use?

0.1.16 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-stream have?

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

0 vulnerabilities were recorded for twitter-stream in the last 12 months, and the oldest entry in this database dates to 29 Mar 2021. 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-stream 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-stream for upcoming vulnerabilities?

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

Vulnerability Database · RubyGems · Package report

twitter-stream: vulnerability history, versions and safety

twitter-stream is a package in the RubyGems ecosystem. Vulert records 1 vulnerability for it across 16 releases, first recorded in Mar 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

1 vulnerabilities recorded M1

1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all twitter-stream vulnerabilities

Vulert verdict on twitter-stream 0.1.16 i

Updated on 23 Oct 2026

Careful: 0.1.16 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100

Security Minor issues
Maintenance Slowing
Popularity Not enough data
Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

Current release 0.1.16 — affected i
Vulnerabilities on record 1 over 1 year · 0 in the last year i
Latest disclosure 29 Mar 2021 i
Highest CVSS 5.9 i
With no published fix 1 i
Last release 171 months ago 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for twitter-stream, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
0.1.16	02 Jul 2012	M1	—	No	Details →
0.1.15	10 Apr 2012	M1	—	No	Details →
0.1.14	22 Jun 2011	M1	—	No	Details →
0.1.13	12 Apr 2011	M1	—	No	Details →
0.1.12	15 Mar 2011	M1	—	No	Details →
0.1.11	15 Mar 2011	M1	—	No	Details →
0.1.10	04 Oct 2010	M1	—	No	Details →
0.1.9	30 Sep 2010	M1	—	No	Details →
0.1.8	13 Aug 2010	M1	—	No	Details →
0.1.7	02 Aug 2010	M1	—	No	Details →
0.1.6	19 May 2010	M1	—	No	Details →
0.1.4	01 Dec 2009	M1	—	No	Details →
0.1.3	14 Oct 2009	M1	—	No	Details →
0.1.2	12 Oct 2009	M1	—	No	Details →
0.1.1	11 Oct 2009	M1	—	No	Details →
0.1.0	11 Oct 2009	M1	—	No	Details →

All 16 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

2021 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for twitter-stream

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2020-24392: Improper Certificate Validation in twitter-stream	5.9 medium	No fix published	29 Mar 2021

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