All issues

Search results

PSUseApprovedVerbs should have a RuleSuppressionID

Status: Open.

#2200In PowerShell/PSScriptAnalyzer;

· iRon7 opened on Aug 4, 2026

ValidateRange boundary type vs parameter type check

Status: Open.

#2199In PowerShell/PSScriptAnalyzer;

· tidy-developer opened on Aug 2, 2026

Update the build to use .NET 10

Status: Open.

#2195In PowerShell/PSScriptAnalyzer;

· sdwheeler opened on Jul 23, 2026

Invoke-ScriptAnalyzer does not report a parse failure in a param() block caused by a missing parameter separator comma.

Status: Open.

#2192In PowerShell/PSScriptAnalyzer;

· FabrizioMarana opened on Jul 17, 2026

PSAvoidUsingConvertToSecureStringWithPlainText makes unreasonable claims at high severity

Status: Open.

#2187In PowerShell/PSScriptAnalyzer;

· et1975 opened on Jun 18, 2026

Additional settings file for developement

Status: Open.

#2184In PowerShell/PSScriptAnalyzer;

· iRon7 opened on May 7, 2026

[Formatter] Indent Right(hand side) CommandExpressionAst

Status: Open.

#2175In PowerShell/PSScriptAnalyzer;

· iRon7 opened on Apr 20, 2026

PSUseDeclaredVarsMoreThanAssignments and assigning multiple variables

Area - PSUseDeclaredVarsMoreThanAssignments

Up-for-Grabs

Status: Open.

#2164In PowerShell/PSScriptAnalyzer;

· iRon7 opened on Mar 17, 2026

PSUseConsistentWhitespace - Ability to ignore if in a line with multiple pipes

Status: Open.

#2162In PowerShell/PSScriptAnalyzer;

· o-l-a-v opened on Mar 7, 2026

Support .config project directory

Area - Engine

Status: Open.

#2157In PowerShell/PSScriptAnalyzer;

· o-l-a-v opened on Feb 21, 2026

Invoke-ScriptAnalyzer-Severity filters rules rather than diagnostics

Status: Open.

#2156In PowerShell/PSScriptAnalyzer;

· liamjpeters opened on Feb 20, 2026

rule request: AvoidPlusEqualToPopulateDictionary

Status: Open.

#2154In PowerShell/PSScriptAnalyzer;

· iRon7 opened on Feb 14, 2026