Vulnerability Database · RubyGems · Package report

stringex: vulnerability history, versions and safety

Q: How do I monitor stringex for upcoming vulnerabilities?

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

stringex is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

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 stringex vulnerabilities

Vulert verdict on stringex 2.8.6 i

Updated on 23 Oct 2026

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

Package health score 77/100

Security No known security issues
Maintenance Slowing
Popularity Not enough data
Community Not enough data

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

Current release 2.8.6 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Last release 42 months ago i
Licence MIT 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for stringex, 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
2.8.6	19 Apr 2023	none	MIT	—	Details →
2.8.5	06 Nov 2018	none	MIT	—	Details →
2.8.4	13 Mar 2018	none	MIT	—	Details →
2.8.3	09 Mar 2018	none	MIT	—	Details →
2.8.2	21 Dec 2017	none	MIT	—	Details →
2.8.1	08 Dec 2017	none	MIT	—	Details →
2.7.1	10 Feb 2017	none	MIT	—	Details →
2.7.0	18 Jan 2017	none	MIT	—	Details →
2.6.1	14 Jul 2016	none	MIT	—	Details →
2.6.0	29 Jan 2016	none	MIT	—	Details →
2.5.2	09 Apr 2014	none	MIT	—	Details →
2.5.1	04 Apr 2014	none	MIT	—	Details →
2.5.0	31 Mar 2014	none	MIT	—	Details →
2.4.2	17 Mar 2014	none	MIT	—	Details →
2.4.1	17 Mar 2014	none	MIT	—	Details →
2.3.0	11 Mar 2014	none	MIT	—	Details →
2.2.2	10 Mar 2014	none	MIT	—	Details →
2.2.1	03 Mar 2014	none	MIT	—	Details →
2.2.0	03 Feb 2014	none	MIT	—	Details →
2.1.2	25 Nov 2013	none	MIT	—	Details →
2.1.1	13 Nov 2013	none	MIT	—	Details →
2.1.0	17 Sep 2013	none	MIT	—	Details →
2.0.11	27 Aug 2013	none	MIT	—	Details →
2.0.10	27 Aug 2013	none	MIT	—	Details →
2.0.9	26 Aug 2013	none	MIT	—	Details →
2.0.8	31 Jul 2013	none	MIT	—	Details →
2.0.7	29 Jul 2013	none	MIT	—	Details →
2.0.6	24 Jul 2013	none	MIT	—	Details →
2.0.5	16 Jul 2013	none	MIT	—	Details →
2.0.4	15 Jul 2013	none	MIT	—	Details →
2.0.3	17 Jun 2013	none	MIT	—	Details →
2.0.2	03 Jun 2013	none	MIT	—	Details →
2.0.1	03 Jun 2013	none	MIT	—	Details →
2.0.0	03 Jun 2013	none	MIT	—	Details →
1.5.1	30 Nov 2012	none	—	—	Details →
1.5.0	29 Nov 2012	none	—	—	Details →
1.4.0	04 May 2012	none	—	—	Details →
1.3.3	24 Apr 2012	none	—	—	Details →
1.3.2	16 Feb 2012	none	—	—	Details →
1.3.1	16 Feb 2012	none	—	—	Details →
1.3.0	08 Aug 2011	none	—	—	Details →
1.2.2	06 Jul 2011	none	—	—	Details →
1.2.1	14 Mar 2011	none	—	—	Details →
1.2.0	20 Oct 2010	none	—	—	Details →
1.1.0	12 Oct 2009	none	—	—	Details →
1.0.3	21 Aug 2009	none	—	—	Details →
1.0.1	20 Aug 2009	none	—	—	Details →
1.0.2	20 Aug 2009	none	—	—	Details →
1.0.0	05 Aug 2009	none	—	—	Details →

All 49 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for stringex

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 stringex

Is stringex safe to use?

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

Vulert scores stringex 77/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 stringex affected?

No. 2.8.6, 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 stringex should I use?

2.8.6 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 stringex have?

0 vulnerabilities are recorded for stringex 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 stringex vulnerabilities disclosed?

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

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