forked from openai/codex
## Why PowerShell safety checks can mistake a literal `start` argument for a URL-launch command, or combine a process launch with a URL from a separate command. ## What changed Classify independently parsed literal PowerShell commands separately so commands such as `Write-Output start 'https://example.com'` do not trigger URL-launch checks. Retain conservative checks for pipelines, script state, executable strings, and shell or terminal wrappers, while continuing to detect actual URL launches and destructive commands. ## Testing Add policy regression coverage for literal arguments, separate commands, URL launches, wrappers, and destructive commands, plus a Windows integration test covering execution and policy rejection. GitOrigin-RevId: 2878aa86bc36b44c60230cc1de3430922b28b81a |
History
|
|
|---|---|---|
| .. | ||
| fixtures | ||
| is_dangerous_command.rs | ||
| mod.rs | ||
| powershell_parser.ps1 | ||
| powershell_parser.rs | ||
| powershell_tree_sitter.rs | ||
| powershell_tree_sitter_tests.rs | ||
| windows_dangerous_commands.rs | ||