Download ScriptAnalyzer from PowerShellGallery
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 17%
Response Time: 1d
First Timer Success: -
PowerShell/PSScriptAnalyzer has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PowerShell/PSScriptAnalyzer respond to incoming external pull requests in approximately 33.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 47.6 places PowerShell/PSScriptAnalyzer in the B tier.
The external contributor pull request merge rate for PowerShell/PSScriptAnalyzer is 16.7%, based on public PR activity from non-core contributors.
PowerShell/PSScriptAnalyzer currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in PowerShell/PSScriptAnalyzer welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/PowerShell/PSScriptAnalyzer?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~21 hours (21% approval). Large PRs (>500 lines) take ~158 hours (15% approval). Keep your diff compact for rapid review.
Summary of the new feature Add EditorConfig .editorconfig to the project, like other PowerShell related repos already have. https://github.com/PowerShell/PowerShell/blob/master/.editorconfig https://github.com/PowerShell/PSResourceGet/blob/master/.editorconfig https://github.com/PowerShell/vscode-powershell/blob/main/.editorconfig Proposed technical implementation details (optional) Unify style, syntax, rules, linting, formatting across PowerShell related projects. What is the latest version of PSScriptAnalyzer at the point of writing Not relevant.
Aside from the false positive issues with the PSUseDeclaredVarsMoreThanAssignments rule, it has also a false negative bug: This concerns assigning multiple variables: This (as the only script line), correctly reports a PSUseDeclaredVarsMoreThanAssignments volitation on $a: $a = $null But this doesn't: $a, $b = $null PSScriptAnalyzer version: 1.24.0 Name Value ---- ----- PSVersion 7.5.4 PSEdition Core GitCommitId 7.5.4 OS Microsoft Windows 10.0.26100 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0
Summary of the new feature Add compatibility profiles for current PowerShell Core versions, Windows 11, Windows PowerShell on Windows 11, potentially other supported OS/PowerShell combinations as outlined by https://learn.microsoft.com/en-us/powershell/scripting/install/powershell-support-lifecycle As a user, I would like to be able to leverage the PSUseCompatibleCommands check against profiles reflecting the current state of the OS and PowerShell, rather than only dated profiles reflecting unsupported OS and PowerShell versions. I am not proposing removal of any old profiles, just creation of new ones and relocation of unsupported ones to the optional directory. Proposed technical implementation details (optional) It would be nice if the process to generate these was added to the CI process, so that as Windows and PS Core versions move forward, new profiles are automatically generated. What is the latest version of PSScriptAnalyzer at the point of writing 1.24.0
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to PowerShell/PSScriptAnalyzer, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of PowerShell/PSScriptAnalyzer acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 16.7% were successfully merged into the primary branch.
PowerShell/PSScriptAnalyzer has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 47.6 places PowerShell/PSScriptAnalyzer in the Solid tier.
The external pull request merge rate is 16.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, PowerShell/PSScriptAnalyzer currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for PowerShell/PSScriptAnalyzer are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.