Mine your Claude Code and Codex logs into a local you.md agent profile.
C-Rank Grade: B (Solid) - 50/100
External PR Merge Rate: 42%
Response Time: 3d
First Timer Success: 33%
ohad6k/emulo has a recorded first-timer success rate of 33.3%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ohad6k/emulo respond to incoming external pull requests in approximately 78.3 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 49.8 places ohad6k/emulo in the B tier.
The external contributor pull request merge rate for ohad6k/emulo is 41.7%, based on public PR activity from non-core contributors.
ohad6k/emulo currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Python project in ohad6k/emulo 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/ohad6k/emulo?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~51 hours (52% approval). Large PRs (>500 lines) take ~376 hours (19% approval). Keep your diff compact for rapid review.
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.
Awesome samples for Volcengine AgentKit Platform with VeADK.
An object-oriented algebraic modeling language in Python for structured optimization problems.
LINE Messaging API SDK for Python
Contributors can find open work, but the repository does not yet explain the privacy boundary or what evidence a safe Ditto contribution needs. Add a small contributor baseline that makes useful participation easier without inviting anyone to upload private logs or generated profiles. Acceptance criteria Add CONTRIBUTING.md with local setup, the full test command, focused-test examples, and the expected verification report. State clearly that raw sessions, generated profiles, receipts, secrets, and local paths must never be committed or attached to an issue. Add issue templates for bugs, source-adapter requests, and documentation/feedback. Make templates ask for minimal redacted reproduction details and environment/version evidence. Add a pull request template with scope, tests run, privacy review, and documentation-impact checks. Add a standard code of conduct and a clear reporting contact. Preserve the existing issue forms and repository behavior if any appear before implementation.
Ditto currently reads Codex and Claude Code JSONL logs. Good next adapters: Cursor Cline Continue Windsurf Best contribution: document where the tool stores local sessions; add a tiny parser path in ditto.py; include a redacted/minimal fixture shape if possible; never commit private logs. If you know one of these formats, comment with the local path and sample schema first.
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 ohad6k/emulo, 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 ohad6k/emulo acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 41.7% were successfully merged into the primary branch.
ohad6k/emulo has a recorded first-timer success rate of 33.3%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 49.8 places ohad6k/emulo in the Solid tier.
The external pull request merge rate is 41.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ohad6k/emulo 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 ohad6k/emulo 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.