refactor: replace unmaintained rust unic-* crates and address RUSTSEC-2025-0094 advisory - #337
Merged
pemistahl merged 9 commits intoNov 14, 2025
Conversation
to address https://rustsec.org/advisories/RUSTSEC-2025-0094.html instead of using the recommended `icu_properties` crate in the advisory which has a big dependency tree, use a lighter weight approach, using the maintained`unicode-general-category` and creating a custom lightweight CharRange implementation.
…al-category to 1.1.0
Owner
|
Thank you, this is indeed useful to replace unmaintained dependencies. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See https://rustsec.org/advisories/RUSTSEC-2025-0094.html
Instead of using the recommended
icu_propertiescrate in the advisory which has a big dependency tree, use a lighter weight approach, using the maintainedunicode-general-categoryand creating a custom lightweight CharRange implementation.resolves #331