GeezerVison

PR Summary

Make analyzer diagnostics more precise and preserve the layout of scripts when applying formatting corrections.

Contributed by Christopher Huffman (@HuffmanStacks) with Codex assistance.

• Put missing BOM diagnostics at line 1, column 1. Fixes Missing line number in rule PSUseBOMForUnicodeEncodedFile #1859.
• Respect disabled pipeline binding and allow an end block to consume $input intentionally. Fixes UseProcessBlockForPipelineCommand returns a warning when pipeline behavior is explicitly disabled #1725 and [Repost] PSUseProcessBlockForPipelineCommand does not recognize use of $input within an End block #1915.
• Report an empty custom rule path through WriteError so Get-ScriptAnalyzerRule honors -ErrorAction. Fixes Get-ScriptAnalyzerRule throws exception despite common parameter '-ErrorAction SilentlyContinue' is defined #1876.
• Apply the inner-brace whitespace rule consistently to both sides of nonempty hashtables. Fixes PSUseConsistentWhitespace CheckInnerBrace - false positive on hashtable closing brace #1742.
• Preserve existing LF and CRLF separators in mixed-ending scripts and use the first separator style for inserted lines. Fixes Cannot determine line endings as the text probably contain mixed line endings. #2074.
• Match Cred and Creds as identifier words and document the credential-name matching rules. Fixes Any variable containing the word "credit" triggers PSAvoidUsingPlainTextForPassword #1886 and AvoidUsingPlainTextForPassword docs do not cover all checked parameter names #1565.
• Replace numbered rule-index link labels with stable names while keeping all 80 link destinations. Fixes The new docs\Rules\README.md format causes merge issues #2220.

Each change is in a separate commit for review.

Validation

• 182 focused Pester tests passed on Linux with each of PowerShell 7.4.14 and 7.6.6.
• The broader Linux suite passed 2,142 tests, with 163 skipped. Four tests failed on both the baseline and the branch because the runner could not resolve the PowerShell process path. All four CLI behaviors passed when replayed with the executable path.
• The Engine and Rules assemblies were compiled with the .NET 8 SDK compiler. Windows and macOS validation is pending upstream CI.
• PSScriptAnalyzer reported zero findings across five selected rules on the eight changed PowerShell files.

PR Checklist

• Meaningful title and summarized changes
• Existing source copyright headers retained
• Regression tests and documentation updated where applicable