unicode-hygiene

Scan files for hidden Unicode characters by running a Python script that detects tag characters, bidirectional overrides, and zero-width characters to ensure file integrity before commits. This prevents supply-chain attacks by identifying visually-spoofed code.

Bidirectional overrides and zero-width characters are non-printing Unicode threats used to visually spoof source code. They hide malicious instructions or alter text display, creating supply-chain vulnerabilities that compromise file integrity during security reviews.

Yes, you can detect mixed-script identifiers using stdlib Python scripts without external dependencies. This approach scans files to identify visually-spoofed Unicode and prevents supply-chain attacks before pushing a skill or plugin.

Pre-commit scanning for supply-chain attacks does not require external security tools. It applies stdlib Python scripts to detect non-printing Unicode threats, ensuring file auditing and security reviews function without adding dependencies to your environment.

Audit files for visually-spoofed Unicode before publishing to prevent supply-chain attacks. Hidden tag characters and bidirectional overrides can inject invisible instructions, compromising file integrity and security when others use your published code.

The best way to prevent invisible Unicode threats is to run a pre-commit scan that identifies tag characters, bidirectional overrides, and zero-width characters. This file auditing process ensures repository integrity before pushing code.