:cloud: :zap: Granular, Actionable Adversary Emulation for the Cloud
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 84%
Response Time: 4d
First Timer Success: 100%
DataDog/stratus-red-team has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in DataDog/stratus-red-team respond to incoming external pull requests in approximately 101.8 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 60.7 places DataDog/stratus-red-team in the A tier.
The external contributor pull request merge rate for DataDog/stratus-red-team is 83.9%, based on public PR activity from non-core contributors.
DataDog/stratus-red-team currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly encouraging & supportive maintainers (75% positive review sentiment). Active code reviews with constructive guidance for new contributors in DataDog/stratus-red-team.
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/DataDog/stratus-red-team?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 07:00 UTC (07: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 ~66 hours (96% approval). Large PRs (>500 lines) take ~489 hours (38% approval). Keep your diff compact for rapid review.
https://aws.amazon.com/blogs/aws/introducing-amazon-ebs-volume-clones-across-aws-accounts/ Study feasibility and pre-conditions Warm-up: EBS volume available Detonation: share it cross-account Clarify differences with https://stratus-red-team.cloud/attack-techniques/AWS/aws.exfiltration.ec2-share-ebs-snapshot/ (sounds like it's the ability to share a live volume vs snapshot)
What is not working? In April, AWS rolled out a default setting blocking client side encryption of objects in newly created buckets: https://docs.aws.amazon.com/AmazonS3/latest/userguide/blocking-unblocking-s3-c-encryption-gpb.html This prevent the detonation from running the CopyObject function with SSE-C parameters What is your Stratus Red Team version? latest Full output? api error AccessDenied: ... is not authorized to perform: s3:CopyObject on resource: "arn:aws:s3:::stratus-red-team-ransomware-bucket-.../aerospace-ogle.png" because this bucket has blocked upload requests that specify Server Side Encryption with Customer provided keys (SSE-C). Proposed solution Disable the encryption blocking, either at warmup to simulate a bucket vulnerable, or at detonation time to simulate an attacker removing the protection (but that can be a ttp on its own)
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 DataDog/stratus-red-team, 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 DataDog/stratus-red-team acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.9% were successfully merged into the primary branch.
DataDog/stratus-red-team has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming 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 60.7 places DataDog/stratus-red-team in the Welcoming tier.
The external pull request merge rate is 83.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, DataDog/stratus-red-team currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for DataDog/stratus-red-team 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.