#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

#193 in Text processing

Download history 47420/week @ 2024-11-16 47211/week @ 2024-11-23 41631/week @ 2024-11-30 41852/week @ 2024-12-07 42128/week @ 2024-12-14 26204/week @ 2024-12-21 27481/week @ 2024-12-28 39522/week @ 2025-01-04 41982/week @ 2025-01-11 36749/week @ 2025-01-18 35520/week @ 2025-01-25 40067/week @ 2025-02-01 44173/week @ 2025-02-08 52818/week @ 2025-02-15 55111/week @ 2025-02-22 54636/week @ 2025-03-01

214,045 downloads per month
Used in 96 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