PySpector is a static analysis security testing (SAST) Framework engineered for modern Python development workflows. It leverages a powerful Rust core to deliver high-speed, accurate vulnerability scanning, wrapped in a developer-friendly Python CLI.
C-Rank Grade: B (Solid) - 56/100
External PR Merge Rate: 64%
Response Time: 4d
First Timer Success: 50%
ParzivalHack/PySpector has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ParzivalHack/PySpector respond to incoming external pull requests in approximately 96.6 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 56.5 places ParzivalHack/PySpector in the B tier.
The external contributor pull request merge rate for ParzivalHack/PySpector is 63.6%, based on public PR activity from non-core contributors.
ParzivalHack/PySpector currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
PySpector is a static analysis security testing (SAST) Framework engineered for modern Python development workflows. It leverages a powerful Rust core to deliver high-speed, accurate vulnerability scanning, wrapped in a developer-friendly Python CLI.
Active maintainer team in ParzivalHack/PySpector 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/ParzivalHack/PySpector?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 10:00 UTC (10:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~63 hours (80% approval). Large PRs (>500 lines) take ~464 hours (29% approval). Keep your diff compact for rapid review.
After recently implementing a new SKILL.md to allow agentic tools to perform security audits of Python codebases, via PySpector, we were able to test and validate the skill only on Claude Code so far, so our current documentation about this skill, lacks instructions on how to add and run the skill on other agentic tools like OpenAI Codex and Google Antigravity, and we need some help in testing that skill on any of those agentic tools, and then update our README.md documentation accordingly with the skill setup instructions :)
PySpector includes a dedicated set of AI/LLM security rules. We want to expand coverage with additional patterns related to prompt injection, unsafe agent behavior, or insecure model usage. This issue is suitable for first-time contributors. What to do: Propose a new (valid) AI/LLM-related rule (check that a rule for that exact class of vulnerability isnt already present in the current AI ruleset) Implement it using the existing rule format Add a small test case or example Document the rule behavior briefly No Rust knowledge required. Python and basic static analysis understanding is enough. Help from mantainers is available through review :)
PySpector runs a VDP (Vulnerability Disclosure Program) that allows any Security Researcher to easily submit reports (via GHSA) for vulnerabilities found in PySpector's codebase. We already awarded multiple CVEs (that you can find published here: https://github.com/ParzivalHack/PySpector/security/advisories) to researchers who found real vulnerabilities in PySpector codebase, so if you're a security researcher, or a developer who understands product vulnerabilities in source code, and you want to get your first (or latest) CVE, while improving the security posture of PySpector, read our SECURITY.md policy, and if you think you've found a real security vulnerability, send us a report here, via Github Security Advisory: https://github.com/ParzivalHack/PySpector/security/advisories/new
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 ParzivalHack/PySpector, 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 ParzivalHack/PySpector acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.6% were successfully merged into the primary branch.
ParzivalHack/PySpector has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 56.5 places ParzivalHack/PySpector in the Solid tier.
The external pull request merge rate is 63.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ParzivalHack/PySpector currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ParzivalHack/PySpector 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.