#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

#173 in Text processing

Download history 29602/week @ 2024-09-22 29181/week @ 2024-09-29 27182/week @ 2024-10-06 29787/week @ 2024-10-13 36441/week @ 2024-10-20 38872/week @ 2024-10-27 45268/week @ 2024-11-03 45432/week @ 2024-11-10 47269/week @ 2024-11-17 46674/week @ 2024-11-24 41684/week @ 2024-12-01 41915/week @ 2024-12-08 42477/week @ 2024-12-15 25086/week @ 2024-12-22 28040/week @ 2024-12-29 36451/week @ 2025-01-05

135,405 downloads per month
Used in 85 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
~42K SLoC