The recent breaking change to Invoke-WebRequest in Windows PowerShell 5.1 has the potential to affect a lot of automation, especially in older environments. To make it easier to assess the impact, I published a script called Search-CmdletParameterUsage.ps1.

This tool recursively scans your scripts and modules for any cmdlet + parameter usage. While I built it to identify places where Invoke-WebRequest is not using -UseBasicParsing, it works generically for any cmdlet you're concerned about.

If you maintain large codebases or inherited automation, this can save a ton of manual review.

Script: https://gist.github.com/mdowst/9d00ff37ea79dcbfb98e6de580cbedbe

KB on the breaking change:
https://support.microsoft.com/en-us/topic/powershell-5-1-preventing-script-execution-from-web-content-7cb95559-655e-43fd-a8bd-ceef2406b705

Happy scripting! And good luck hunting down those IWR calls.