#unicode #security #unicode-text #text

unicode-security

Detect possible security problems with Unicode usage according to Unicode Technical Standard #39 rules

9 releases

0.1.2 Sep 12, 2024
0.1.1 Feb 9, 2024
0.1.0 Sep 15, 2022
0.0.6 Dec 23, 2021
0.0.2 Jan 2, 2020

#144 in Text processing

Download history 42352/week @ 2024-10-30 44222/week @ 2024-11-06 47298/week @ 2024-11-13 48136/week @ 2024-11-20 43958/week @ 2024-11-27 40438/week @ 2024-12-04 42154/week @ 2024-12-11 36664/week @ 2024-12-18 23775/week @ 2024-12-25 33939/week @ 2025-01-01 40108/week @ 2025-01-08 40871/week @ 2025-01-15 34764/week @ 2025-01-22 37332/week @ 2025-01-29 42554/week @ 2025-02-05 36734/week @ 2025-02-12

157,586 downloads per month
Used in 95 crates (via cedar-policy-validator)

MIT/Apache

455KB
5K SLoC

unicode-security

Build Status Current Version License: MIT/Apache-2.0

This crate exposes various utilities from UAX #39 Unicode Security Mechanisms


lib.rs:

Detect possible security problems with Unicode usage according to Unicode Technical Standard #39 rules.

extern crate unicode_security;

use unicode_security::GeneralSecurityProfile;

fn main() {
    let ch = 'µ'; // U+00B5 MICRO SIGN
    let allowed = 'µ'.identifier_allowed();
    println!("{}", ch);
    println!("The above char is {} in unicode identifiers.",
             if allowed { "allowed" } else { "restricted" });
}

features

unicode-security supports a no_std feature. This eliminates dependence on std, and instead uses equivalent functions from core.

crates.io

You can use this package in your project by adding the following to your Cargo.toml:

[dependencies]
unicode-security = "0.0.1"

Dependencies

~1.5MB
~43K SLoC