A community repository of PowerShell Scanners for PDQ Inventory.
C-Rank Grade: B (Solid) - 45/100
External PR Merge Rate: 100%
Response Time: 3d
First Timer Success: -
pdqcom/PowerShell-Scanners 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 pdqcom/PowerShell-Scanners respond to incoming external pull requests in approximately 70.9 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 45.5 places pdqcom/PowerShell-Scanners in the B tier.
The external contributor pull request merge rate for pdqcom/PowerShell-Scanners is 100.0%, based on public PR activity from non-core contributors.
pdqcom/PowerShell-Scanners currently has 21 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A community repository of PowerShell Scanners for PDQ Inventory.
Collaborative maintainer environment in pdqcom/PowerShell-Scanners. Reviews community pull requests with focus on project quality.
Discussions in pdqcom/PowerShell-Scanners focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/pdqcom/PowerShell-Scanners?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~46 hours (96% approval). Large PRs (>500 lines) take ~340 hours (45% approval). Keep your diff compact for rapid review.
Marked Yes but test for PDQ Connect in the scanner README. Goal: Create or update a Connect-Windows Defender Threats.ps1 script if the scanner can work in PDQ Connect. If the scanner is not a fit for Connect, test it, document the limitation, and close the issue with the result. Reference: Scanner README: Windows Defender Threats Main compatibility list: README.md
Marked maybe for PDQ Connect in the scanner README. Goal: Create or update a Connect-Mapped Printers.ps1 script if the scanner can work in PDQ Connect. If the scanner is not a fit for Connect, test it, document the limitation, and close the issue with the result. Reference: Scanner README: Mapped Printers Main compatibility list: README.md
Marked I think it does, gotta test for PDQ Connect in the scanner README. Goal: Create or update a Connect-Mapped Drives.ps1 script if the scanner can work in PDQ Connect. If the scanner is not a fit for Connect, test it, document the limitation, and close the issue with the result. Reference: Scanner README: Mapped Drives Main compatibility list: README.md
Marked probably on your IIS servers for PDQ Connect in the scanner README. Goal: Create or update a Connect-IIS App Pools.ps1 script if the scanner can work in PDQ Connect. If the scanner is not a fit for Connect, test it, document the limitation, and close the issue with the result. Reference: Scanner README: IIS App Pools Main compatibility list: README.md
Marked Yes, check more first for PDQ Connect in the scanner README. Goal: Create or update a Connect-Hosts File.ps1 script if the scanner can work in PDQ Connect. If the scanner is not a fit for Connect, test it, document the limitation, and close the issue with the result. Reference: Scanner README: Hosts File Main compatibility list: README.md
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 pdqcom/PowerShell-Scanners, 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 pdqcom/PowerShell-Scanners acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
pdqcom/PowerShell-Scanners 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 ~2 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 45.5 places pdqcom/PowerShell-Scanners in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, pdqcom/PowerShell-Scanners currently has 21 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for pdqcom/PowerShell-Scanners 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.