Vulnerability Database · RubyGems · Package report

split: vulnerability history, versions and safety

Q: How do I monitor split for upcoming vulnerabilities?

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

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

Vulert verdict on split 4.0.5 i

Updated on 23 Oct 2026

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

Package health score 74/100

Security Minor issues
Maintenance Maintaining
Popularity Key ecosystem project
Community Quiet

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

Current release 4.0.5 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 2,708 i
OpenSSF scorecard 3/10 i
Last release 14 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 split, 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
4.0.5	04 Aug 2025	none	MIT	—	Details →
4.0.4	03 Mar 2024	none	MIT	—	Details →
4.0.3	15 Nov 2023	none	MIT	—	Details →
4.0.2	02 Dec 2022	none	MIT	—	Details →
4.0.1	30 Dec 2021	none	MIT	—	Details →
4.0.0.pre2	07 Nov 2021	none	MIT	—	Details →
4.0.0.pre	17 Dec 2020	none	MIT	—	Details →
3.4.1	12 Nov 2019	none	MIT	—	Details →
3.4.0	10 Nov 2019	none	MIT	—	Details →
3.3.2	12 Apr 2019	none	MIT	—	Details →
3.3.1	11 Jan 2019	none	MIT	—	Details →
3.3.0	13 Aug 2018	none	MIT	—	Details →
3.2.0	21 Sep 2017	none	MIT	—	Details →
3.1.1	30 Aug 2017	none	MIT	—	Details →
3.1.0	14 Aug 2017	none	MIT	—	Details →
3.0.0	30 Mar 2017	none	MIT	—	Details →
2.2.0	11 Nov 2016	none	MIT	—	Details →
2.1.0	08 Aug 2016	none	MIT	—	Details →
2.0.0	17 Jul 2016	none	MIT	—	Details →
1.7.0	28 Jun 2016	none	MIT	—	Details →
1.6.0	16 Jun 2016	none	MIT	—	Details →
1.5.0	08 Jun 2016	none	MIT	—	Details →
1.4.5	07 Jun 2016	none	MIT	—	Details →
1.4.4	09 May 2016	none	MIT	—	Details →
1.4.3	28 Apr 2016	none	MIT	—	Details →
1.4.2	25 Apr 2016	none	MIT	—	Details →
1.4.1	21 Apr 2016	none	MIT	—	Details →
1.4.0	02 Apr 2016	none	MIT	—	Details →
1.3.2	02 Jan 2016	none	MIT	—	Details →
1.3.1	01 Jan 2016	none	MIT	—	Details →
1.3.0	20 Oct 2015	none	MIT	—	Details →
1.2.1	17 May 2015	none	MIT	—	Details →
1.2.0	24 Jan 2015	none	MIT	—	Details →
1.1.0	09 Jan 2015	none	MIT	—	Details →
1.0.0	12 Oct 2014	none	MIT	—	Details →
0.8.0	25 Sep 2014	none	MIT	—	Details →
0.7.3	16 Sep 2014	none	MIT	—	Details →
0.7.2	12 Jun 2014	none	MIT	—	Details →
0.7.1	20 Mar 2014	none	MIT	—	Details →
0.7.0	26 Dec 2013	none	MIT	—	Details →
0.6.6	14 Oct 2013	none	MIT	—	Details →
0.6.5	23 Aug 2013	none	MIT	—	Details →
0.6.4	08 Aug 2013	none	—	—	Details →
0.6.3	08 Jul 2013	none	—	—	Details →
0.6.2	06 Jun 2013	none	—	—	Details →
0.6.1	04 May 2013	none	—	—	Details →
0.6.0	04 Apr 2013	none	—	—	Details →
0.5.0	28 Jan 2013	none	—	—	Details →
0.4.6	28 Oct 2012	none	—	—	Details →
0.4.5	30 Aug 2012	none	—	—	Details →
0.4.4	09 Aug 2012	none	—	—	Details →
0.4.3	08 Jul 2012	none	—	—	Details →
0.4.2	01 Jun 2012	none	—	—	Details →
0.4.1	06 Apr 2012	none	—	—	Details →
0.4.0	07 Mar 2012	none	—	—	Details →
0.3.3	16 Feb 2012	none	—	—	Details →
0.3.2	12 Feb 2012	none	—	—	Details →
0.3.1	19 Nov 2011	none	—	—	Details →
0.3.0	09 Oct 2011	none	—	—	Details →
0.2.4	18 Jul 2011	none	—	—	Details →
0.2.3	26 Jun 2011	none	—	—	Details →
0.2.2	11 Jun 2011	none	—	—	Details →
0.2.1	29 May 2011	none	—	—	Details →
0.1.1	18 May 2011	none	—	—	Details →
0.1.0	17 May 2011	none	—	—	Details →

All 65 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 split

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 split

Is split safe to use?

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

Vulert scores split 74/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 split affected?

No. 4.0.5, 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 split should I use?

4.0.5 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 split have?

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

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

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