PSScriptAnalyzer icon indicating copy to clipboard operation
PSScriptAnalyzer copied to clipboard

Download ScriptAnalyzer from PowerShellGallery

Results 201 PSScriptAnalyzer issues
Sort by recently updated
recently updated
newest added

When running the command provided in the reproduce an exception is thrown. This is unexpected and undesirable. It would be great when exceptions could be silenced by specifying common parameter...

Issue-Bug

## PR Summary Addition of rule to advise users against using catch blocks with type RuntimeException. Reason for rule is catch blocks with type RuntimeException catch any type of exception...

Before submitting a bug report: - Make sure you are able to repro it on the latest released version - Perform a quick search for existing issues to check if...

Issue - Enhancement
Area - Rule Sets

**Summary of the new feature** As someone who writes a lot of C code and is a big fan of clang-format's `AlignConsecutiveAssignments`, I'm also a big fan of `Invoke-Formatter`'s PSAlignAssignmentStatement...

Up-for-Grabs
Area - Formatter
Issue-Enhancement

Currently the `-Fix` `-Confirm` (and `-WhatIf`) common parameters aren't very specific on what and how PSScriptAnalyzer is about to correct the found violations: ```PowerShell invoke-scriptanalyzer .\Test.ps1 -fix -Confirm Confirm Are...

Area - Engine
Issue-Enhancement

Line numbers are missing for the Rule "Missing Line Number for PSUseBOMForUnicodeEncodedFile" Steps to reproduce ------------------ Introduce a file test.ps1 with the following content: ```PowerShell Get–ChildItem ``` Run the PSScriptAnalyzer...

Area - Rules
Issue-Bug

I am writing [custom rules](https://github.com/lzybkr/PesterAnalyzerRules) and I see an error reported twice when there should be just one report. I invoke script analyzer like this: ```powershell #11 PS> Invoke-ScriptAnalyzer -CustomRulePath...

Issue - Discussion
Area - Engine

As for [AvoidUsingConvertToSecureStringWithPlainText](https://learn.microsoft.com/powershell/utility-modules/psscriptanalyzer/rules/avoidusingconverttosecurestringwithplaintext?view=ps-modules) it should be avoided to retrieve a **PlainText** password *from* a `SecureString` as it might leave memory trials (or even logging trails). ```PowerShell $Password = $SecureString |...

Issue - New Rule
Issue-Enhancement
Up for Grabs

## Summary of the new feature Remembering the days behind my TRS-80 where the first versions only had a `6` bit character set of `64` characters. A few years later,...

Issue - Discussion
Issue - New Rule
Issue-Enhancement

### Prerequisites - [X] I have written a descriptive issue title. - [X] I have searched all [_open and closed_ issues](https://github.com/PowerShell/vscode-powershell/issues?q=is%3Aissue) to ensure it has not already been reported. -...

Area - Rules
Issue-Bug
Up for Grabs