Ouroboros — self-creating AI agent. Born Feb 16, 2026.
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 75%
Response Time: 1d
First Timer Success: 50%
razzant/ouroboros has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in razzant/ouroboros respond to incoming external pull requests in approximately 25.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 62.5 places razzant/ouroboros in the A tier.
The external contributor pull request merge rate for razzant/ouroboros is 75.2%, based on public PR activity from non-core contributors.
razzant/ouroboros currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
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/razzant/ouroboros?utm_source=github&utm_medium=badge)
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Python.
Ultralytics YOLO26, YOLO11, YOLOv8 — object detection, instance segmentation, semantic segmentation, image classification, pose estimation, object tracking
AI observability platform for production LLM and agent systems.
Indico - A feature-rich event management system, made @ CERN, the place where the Web was born.
What need would this address? A Windows user running the official v6.100.0 package reported a Kaspersky Standard PDM:Trojan.Win32.Generic behavioral detection against: Ouroboros\_internal\python-standalone\python.exe The alert appeared when Cursor was connected. Current evidence strongly suggests a false positive rather than a compromised release: The official Windows ZIP is bound to tag v6.100.0 / commit 944ad989921213dc8394ad09f7dc836e3eed36e3 and has SHA-256 ea0e1fbe1448fbb8dc2492e494129632cdc30c6719db66f1e436b3fefaa7c4b4. The bundled python.exe has SHA-256 fdfbf8f7d056a13e80460979a13aaf4528577f52b6141bb3dc3732cff7bd7cd6 and is byte-for-byte identical to the CPython 3.10.19 executable from the digest-pinned astral-sh/python-build-standalone archive used by the build. Kaspersky OpenTIP reports this exact file as Clean, while VirusTotal currently reports 0/72 static detections. Connecting Cursor legitimately makes the embedded Python verify or extract executable runtimes, start the
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 razzant/ouroboros, 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 razzant/ouroboros acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.2% were successfully merged into the primary branch.
razzant/ouroboros has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming 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 62.5 places razzant/ouroboros in the Welcoming tier.
The external pull request merge rate is 75.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, razzant/ouroboros 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 razzant/ouroboros 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.