Vulnerability Database · RubyGems · Package report
unicode-display_width: vulnerability history, versions and safety
unicode-display_width is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the RubyGems ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on unicode-display_width 3.3.0 i
Updated on 23 Oct 2026
Good news: 3.3.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on 3.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 3.3.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 139 i
- OpenSSF scorecard 2/10 i
- Last release 1 month 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.
01 Versions
Which versions are affected
Every version Vulert tracks for unicode-display_width, 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.
- 3.3.0 20 Sep 2026
- 3.2.0 09 Sep 2025
- 3.1.5 15 Aug 2025
- 3.1.4 13 Jan 2025
- 3.1.3 26 Dec 2024
- 3.1.2 20 Nov 2024
- 3.1.1 19 Nov 2024
- 3.1.0 18 Nov 2024
- 3.0.1 13 Nov 2024
- 3.0.0 13 Nov 2024
- 3.0.0.pre 13 Nov 2024
- 2.6.0 13 Sep 2024
- 2.5.0 01 Oct 2023
- 2.4.2 04 Jan 2023
- 2.4.1 03 Jan 2023
- 2.4.0 03 Jan 2023
- 2.3.0 14 Sep 2022
- 2.2.0 24 Jun 2022
- 2.1.0 15 Sep 2021
- 1.8.0 15 Sep 2021
- 2.0.0 30 Dec 2020
- 2.0.0.pre2 11 Mar 2020
- 1.7.0 11 Mar 2020
- 2.0.0.pre1 16 Jan 2020
- 1.6.1 16 Jan 2020
- 1.6.0 08 May 2019
- 1.5.0 05 Mar 2019
- 1.4.1 21 Dec 2018
- 1.4.0 05 Jun 2018
- 1.3.3 28 May 2018
- 1.3.2 19 Apr 2018
- 1.3.1 19 Apr 2018
- 1.3.0 20 Jun 2017
- 1.2.1 10 Apr 2017
- 1.2.0 08 Apr 2017
- 1.1.3 13 Jan 2017
- 1.1.2 09 Dec 2016
- 1.1.1 07 Sep 2016
- 1.1.0 22 Jun 2016
- 1.0.5 30 Apr 2016
- 1.0.4 30 Apr 2016
- 1.0.3 29 Mar 2016
- 1.0.2 10 Mar 2016
- 1.0.1 07 Mar 2016
- 1.0.0 02 Mar 2016
- 0.3.1 06 Jan 2016
- 0.3.0 04 Dec 2015
- 0.2.0 05 Feb 2015
- 0.1.1 05 Jan 2011
- 0.1.0 03 Jan 2011
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 3.3.0 | 20 Sep 2026 | none | MIT | — | Details → |
| 3.2.0 | 09 Sep 2025 | none | MIT | — | Details → |
| 3.1.5 | 15 Aug 2025 | none | MIT | — | Details → |
| 3.1.4 | 13 Jan 2025 | none | MIT | — | Details → |
| 3.1.3 | 26 Dec 2024 | none | MIT | — | Details → |
| 3.1.2 | 20 Nov 2024 | none | MIT | — | Details → |
| 3.1.1 | 19 Nov 2024 | none | MIT | — | Details → |
| 3.1.0 | 18 Nov 2024 | none | MIT | — | Details → |
| 3.0.1 | 13 Nov 2024 | none | MIT | — | Details → |
| 3.0.0 | 13 Nov 2024 | none | MIT | — | Details → |
| 3.0.0.pre | 13 Nov 2024 | none | MIT | — | Details → |
| 2.6.0 | 13 Sep 2024 | none | MIT | — | Details → |
| 2.5.0 | 01 Oct 2023 | none | MIT | — | Details → |
| 2.4.2 | 04 Jan 2023 | none | MIT | — | Details → |
| 2.4.1 | 03 Jan 2023 | none | MIT | — | Details → |
| 2.4.0 | 03 Jan 2023 | none | MIT | — | Details → |
| 2.3.0 | 14 Sep 2022 | none | MIT | — | Details → |
| 2.2.0 | 24 Jun 2022 | none | MIT | — | Details → |
| 2.1.0 | 15 Sep 2021 | none | MIT | — | Details → |
| 1.8.0 | 15 Sep 2021 | none | MIT | — | Details → |
| 2.0.0 | 30 Dec 2020 | none | MIT | — | Details → |
| 2.0.0.pre2 | 11 Mar 2020 | none | MIT | — | Details → |
| 1.7.0 | 11 Mar 2020 | none | MIT | — | Details → |
| 2.0.0.pre1 | 16 Jan 2020 | none | MIT | — | Details → |
| 1.6.1 | 16 Jan 2020 | none | MIT | — | Details → |
| 1.6.0 | 08 May 2019 | none | MIT | — | Details → |
| 1.5.0 | 05 Mar 2019 | none | MIT | — | Details → |
| 1.4.1 | 21 Dec 2018 | none | MIT | — | Details → |
| 1.4.0 | 05 Jun 2018 | none | MIT | — | Details → |
| 1.3.3 | 28 May 2018 | none | MIT | — | Details → |
| 1.3.2 | 19 Apr 2018 | none | MIT | — | Details → |
| 1.3.1 | 19 Apr 2018 | none | MIT | — | Details → |
| 1.3.0 | 20 Jun 2017 | none | MIT | — | Details → |
| 1.2.1 | 10 Apr 2017 | none | MIT | — | Details → |
| 1.2.0 | 08 Apr 2017 | none | MIT | — | Details → |
| 1.1.3 | 13 Jan 2017 | none | MIT | — | Details → |
| 1.1.2 | 09 Dec 2016 | none | MIT | — | Details → |
| 1.1.1 | 07 Sep 2016 | none | MIT | — | Details → |
| 1.1.0 | 22 Jun 2016 | none | MIT | — | Details → |
| 1.0.5 | 30 Apr 2016 | none | MIT | — | Details → |
| 1.0.4 | 30 Apr 2016 | none | MIT | — | Details → |
| 1.0.3 | 29 Mar 2016 | none | MIT | — | Details → |
| 1.0.2 | 10 Mar 2016 | none | MIT | — | Details → |
| 1.0.1 | 07 Mar 2016 | none | MIT | — | Details → |
| 1.0.0 | 02 Mar 2016 | none | MIT | — | Details → |
| 0.3.1 | 06 Jan 2016 | none | MIT | — | Details → |
| 0.3.0 | 04 Dec 2015 | none | MIT | — | Details → |
| 0.2.0 | 05 Feb 2015 | none | MIT | — | Details → |
| 0.1.1 | 05 Jan 2011 | none | — | — | Details → |
| 0.1.0 | 03 Jan 2011 | none | — | — | Details → |
All 50 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 unicode-display_width
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
Questions
About unicode-display_width
Is unicode-display_width safe to use?
Vulert has no vulnerabilities on record for unicode-display_width 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 unicode-display_width's Vulert package health score?
Vulert scores unicode-display_width 72/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 unicode-display_width affected?
No. 3.3.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 unicode-display_width should I use?
3.3.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 unicode-display_width have?
0 vulnerabilities are recorded for unicode-display_width 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 unicode-display_width vulnerabilities disclosed?
0 vulnerabilities were recorded for unicode-display_width 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 unicode-display_width 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 unicode-display_width for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the unicode-display_width version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.