VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

icu_segmenter: vulnerability history, versions and safety

icu_segmenter is a package in the crates.io ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the crates.io 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 icu_segmenter vulnerabilities

Vulert verdict on icu_segmenter 2.4.0 i

Updated on 23 Oct 2026

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

Package health score 85/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 2.4.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,874 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence Unicode-3.0 i

Version list, release dates, licence and dependants published by crates.io, 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 icu_segmenter, 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
2.4.0 22 Oct 2026 none Unicode-3.0 — Details →
2.3.0 13 Aug 2026 none Unicode-3.0 — Details →
2.2.0 01 Apr 2026 none Unicode-3.0 — Details →
2.1.2 22 Dec 2025 none Unicode-3.0 — Details →
2.0.1 29 Oct 2025 none Unicode-3.0 — Details →
2.1.1 28 Oct 2025 none Unicode-3.0 — Details →
2.1.0 28 Oct 2025 none Unicode-3.0 — Details →
2.0.0 07 May 2025 none Unicode-3.0 — Details →
2.0.0-beta2 26 Feb 2025 none Unicode-3.0 — Details →
2.0.0-beta1 23 Nov 2024 none Unicode-3.0 — Details →
1.5.0 28 May 2024 none Unicode-3.0 — Details →
1.4.0 16 Nov 2023 none non-standard — Details →
1.3.2 03 Oct 2023 none non-standard — Details →
1.3.0 23 Sep 2023 none non-standard — Details →
1.2.1 18 Apr 2023 none Unicode-DFS-2016 — Details →
1.2.0 14 Apr 2023 none Unicode-DFS-2016 — Details →
0.8.0 26 Jan 2023 none Unicode-DFS-2016 — Details →
0.7.0 27 Sep 2022 none Unicode-DFS-2016 — Details →
1.0.0-alpha1 05 Aug 2022 none Unicode-DFS-2016 — Details →
0.6.0 17 May 2022 none non-standard — Details →
0.0.1 29 Apr 2021 none non-standard — Details →

All 21 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 icu_segmenter

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 icu_segmenter

Is icu_segmenter safe to use?

Vulert has no vulnerabilities on record for icu_segmenter in crates.io 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 icu_segmenter's Vulert package health score?

Vulert scores icu_segmenter 85/100, which reads as healthy. 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 icu_segmenter affected?

No. 2.4.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.

How many vulnerabilities does icu_segmenter have?

0 vulnerabilities are recorded for icu_segmenter in the crates.io 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 icu_segmenter vulnerabilities disclosed?

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

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