{"version":"2.1.53","anchor":"bash-command-security-checks-unicode-whitespace-and-mid-word","canonical_anchor":"bash-command-security-checks-unicode-whitespace-and-mid-word","heading":"Bash Command Security Checks: Unicode Whitespace and Mid-Word Hash","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.53\/e\/bash-command-security-checks-unicode-whitespace-and-mid-word","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.53","markdown":"### Bash Command Security Checks: Unicode Whitespace and Mid-Word Hash\n\n**What**\n\nTwo new security checks detect potentially dangerous command patterns before execution.\n\n**Details**\n\n- **Unicode whitespace detection**: Commands containing exotic Unicode whitespace characters (such as non-breaking spaces `\\u00A0`, em spaces `\\u2000-\\u200A`, and others) are now flagged, as these can cause parsing inconsistencies between `shell-quote` and bash\n- **Mid-word hash detection**: Commands containing `#` characters mid-word (e.g., not preceded by whitespace) are flagged because `shell-quote` and bash parse these differently \u2014 bash treats `#` as a comment start in some contexts while `shell-quote` does not\n- Both checks trigger a user confirmation prompt (\"ask\" behavior) rather than blocking outright\n\n**Evidence**\n\nNew security check IDs `UNICODE_WHITESPACE` and `MID_WORD_HASH` (search for `\"UNICODE_WHITESPACE\"` and `\"MID_WORD_HASH\"`)"}