PSScriptAnalyzer provides script analysis and checks for potential code defects in the scripts by applying a group of built-in or customized rules on the scripts being analyzed.

A CMDLet for converting PSScriptAnalyzer output to the SARIF format.

PS Script Analyzer Custom Rules for the DSC Community standards

Contains the PSScriptAnalyzer custom rule PSCustomUseLiteralPath to detect cases when -Path is used instead of -LiteralPath. See https://github.com/jborean93/PSSA-PSCustomUseLiteralPath for more info

Extra rules for PSScriptAnalyzer.

Provides pre-defined pester tests for PowerShell scripts and modules.

Convert PSScriptAnalyzer results to Junit XML

Opinionated PSScriptAnalyzer custom rules

Shared analyzer settings and standards utilities for AtlassianPS modules.

A set of PSScriptAnalyzer rules that help make it Good Enough!

Pipeline-first PSScriptAnalyzer custom rules with helper commands for easy rule-path discovery and analyzer invocation.

Security-focused custom PSScriptAnalyzer rules for PowerShell codebases (OWASP/CWE mapped).

Counts the lines of code based on the compact One True Brace style (requires PSScriptAnalyzer) In -Verbose mode, outputs the OTBS formatted script with line number next to the lines that count

PowerShell module scaffolding and authoring tool with built-in build, test, lint, and CI/CD pipelines.

Test Intune scripts before Intune does: static rules, a runtime harness, Pester assertions, a Graph pre-flight over the tenant's deployed scripts and readers for the agent's logs

Finds deprecated and retired Microsoft 365, Entra ID and Azure PowerShell commands (MSOnline, AzureAD, Exchange RPS, AzureRM, Azure AD Graph, ...) in your scripts and tells you what to use instead. Works as a command, as a PSScriptAnalyzer rule in VS Code and as a GitHub Action.