kenryu42/cc-safety-net v2.7.9

on GitHub

Closes gaps where commands naming a Windows path could read a secret file without being blocked, on Windows in auto mode and under the PowerShell dialect.

Fixed

• Fixed auto shell detection dropping the backslashes of an unquoted Windows path, which let commands such as cat C:\proj\.env, Get-ChildItem ~\OneDrive\.env, Get-ChildItem $env:USERPROFILE\proj\.env, and docker run --env-file=C:\proj\.env img read a secret file unblocked, and kept a custom rule naming a native path from matching. (#339, #337)
• Fixed secret protection reading a path attached to a PowerShell parameter with a colon, so Get-Content -Path:C:\proj\.env and Get-Content -LiteralPath:~\.ssh\id_rsa are now blocked like their space-separated forms. (#340)
• Fixed the policy-file and git-metadata guards missing the same colon-attached form, so a write such as Set-Content -Path:<policy.json> x is now blocked. (#340)
• Fixed explain --shell powershell showing POSIX words in its parse step instead of the PowerShell words it actually analyzed. (#339)