Prowler is the world’s most widely used open-source cloud security platform that automates security and compliance across any cloud environment.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 76%
Response Time: 3d
First Timer Success: 47%
prowler-cloud/prowler has a recorded first-timer success rate of 47.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in prowler-cloud/prowler respond to incoming external pull requests in approximately 61.1 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 66.2 places prowler-cloud/prowler in the A tier.
The external contributor pull request merge rate for prowler-cloud/prowler is 75.7%, based on public PR activity from non-core contributors.
prowler-cloud/prowler currently has 23 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Established Python ecosystem in prowler-cloud/prowler. Maintains structured code review standards for external contributors.
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/prowler-cloud/prowler?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~40 hours (95% approval). Large PRs (>500 lines) take ~293 hours (34% approval). Keep your diff compact for rapid review.
Existing check search I have searched existing issues, Prowler Hub, and the public roadmap, and this check does not already exist. Provider AWS New provider name No response Service or product area cloudwatch Suggested check name cloudwatch_bedrock_agent_alarms_configured Context and goal Source control: FS-11 — Agent Rate Alarms. Semantic requirement: Verifies CloudWatch alarms exist for agent invocation rates. Valid cloud-posture assertion: No check evaluates AWS/Bedrock/Agents invocation or throttling alarms. The proposed check evaluates a durable AWS control-plane property with deterministic resource-level or regional posture semantics; it does not treat optional product adoption or manual governance evidence as failure. Resource scope: Each AWS region with Bedrock Agents, evaluated as one regional posture result. Initiative tracker: #12597 Expected behavior Resource or scope to evaluate: Each AWS region with Bedrock Agents, evaluated as one regional posture result. PASS wh
Existing check search I have searched existing issues, Prowler Hub, and the public roadmap, and this check does not already exist. Provider AWS New provider name No response Service or product area ecr Suggested check name ecr_repository_encrypted_with_cmk Context and goal Source control: AC-05 — Amazon ECR Repository Encryption. Semantic requirement: Validates Amazon ECR repositories use encryption. Valid cloud-posture assertion: No current Prowler check covers ECR repository encryption configuration used by AgentCore. The proposed check evaluates a durable AWS control-plane property with deterministic resource-level or regional posture semantics; it does not treat optional product adoption or manual governance evidence as failure. Resource scope: Each Amazon ECR private repository. Initiative tracker: #12597 Expected behavior Resource or scope to evaluate: Each Amazon ECR private repository. PASS when: encryptionConfiguration.encryptionType is KMS and kmsKey is a customer-man
Existing check search I have searched existing issues, Prowler Hub, and the public roadmap, and this check does not already exist. Provider AWS New provider name No response Service or product area cloudwatch Suggested check name cloudwatch_bedrock_runtime_alarms_configured Context and goal Source control: BR-32 — CloudWatch Alarms on Bedrock Metrics. Semantic requirement: Verifies CloudWatch alarms exist on Amazon Bedrock runtime metrics (the AWS/Bedrock namespace) to detect abuse, denial-of-wallet, sustained throttling, and content-filter spikes. Uses DescribeAlarms and matches alarms that target the AWS/Bedrock namespace directly or via a metric-math expression. Only assessed in regions that have Bedrock resources. Valid cloud-posture assertion: CloudWatch alarms are inventoried, but no check requires AWS/Bedrock runtime alarms or metric-math references. The proposed check evaluates a durable AWS control-plane property with deterministic resource-level or regional posture sema
Existing check search I have searched existing issues, Prowler Hub, and the public roadmap, and this check does not already exist. Provider AWS New provider name No response Service or product area bedrock Suggested check name bedrock_model_invocation_job_output_encrypted_with_cmk Context and goal Source control: BR-31 — Batch Inference Output Encryption. Semantic requirement: Verifies batch inference (model invocation) jobs encrypt their S3 output with a customer-managed KMS key. Reads outputDataConfig.s3OutputDataConfig.s3EncryptionKeyId from the job summaries returned by ListModelInvocationJobs and reports jobs without a customer-managed output key. Valid cloud-posture assertion: Model invocation jobs and S3 output encryption keys are not inventoried. The proposed check evaluates a durable AWS control-plane property with deterministic resource-level or regional posture semantics; it does not treat optional product adoption or manual governance evidence as failure. Resource sco
Existing check search I have searched existing issues, Prowler Hub, and the public roadmap, and this check does not already exist. Provider AWS New provider name No response Service or product area bedrock Suggested check name bedrock_imported_model_encrypted_with_cmk Context and goal Source control: BR-30 — Imported Model Customer-Managed KMS Encryption. Semantic requirement: Complements BR-11/BR-17 by verifying imported custom models use customer-managed KMS keys. Lists imported models and reads GetImportedModel.modelKmsKeyArn, reporting models encrypted with AWS-owned keys instead of a customer-managed key. Valid cloud-posture assertion: Imported models and modelKmsKeyArn are not inventoried. The proposed check evaluates a durable AWS control-plane property with deterministic resource-level or regional posture semantics; it does not treat optional product adoption or manual governance evidence as failure. Resource scope: Each Amazon Bedrock imported model. Initiative tracker:
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 prowler-cloud/prowler, 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 prowler-cloud/prowler acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.7% were successfully merged into the primary branch.
prowler-cloud/prowler has a recorded first-timer success rate of 47.4%. Repositories ranked Welcoming 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 66.2 places prowler-cloud/prowler in the Welcoming tier.
The external pull request merge rate is 75.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, prowler-cloud/prowler currently has 23 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for prowler-cloud/prowler 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.