The open-source robot runtime that records a run, re-executes it against new code, and returns an exit code.
C-Rank Grade: D (Risky) - 30/100
External PR Merge Rate: -
Response Time: <1h
First Timer Success: -
cerulion-inc/cerulion has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in cerulion-inc/cerulion respond to incoming external pull requests in approximately 0.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 29.9 places cerulion-inc/cerulion in the D tier.
The external contributor pull request merge rate for cerulion-inc/cerulion is 0.0%, based on public PR activity from non-core contributors.
cerulion-inc/cerulion does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Strict review standards in cerulion-inc/cerulion. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in cerulion-inc/cerulion focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/cerulion-inc/cerulion?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (81% approval). Large PRs (>500 lines) take ~3 hours (29% approval). Keep your diff compact for rapid review.
Problem cerulion ros2 attach --iface <ip> --dry-run refuses to run outside a workspace: Error: Workspace not found (searched from '/tmp/x' to filesystem root). Create one with: cerulion workspace create <name> --dry-run is documented as "Print the discovery report and stop — write nothing, run nothing", so it needs no workspace. On a robot this forces creating a throwaway workspace just to list DDS topics. Observed CLI 0.2.0 (e0334bd) on a Go2 Orin. After cerulion workspace create in /tmp, the same command printed the full report (67 topics, 38 resolvable). Expected --dry-run works from any directory. Only the write/run path requires a workspace.
Repository instructions name a top-level USER_API.md, but the tracked reference and documentation tests use docs/user-api.md. This caused a review to request a duplicate absent reference even though the actual API document was updated. Update instruction paths and related test comments/error wording to docs/user-api.md. Keep one authoritative reference, verify it exists and run the documentation tests. Verify the mismatch on the canonical baseline before editing; the report originates from the pre-open-source development tree. Public-safe migration summary of cerulion-base#963. The original internal thread retains dated discussion and development history; GitHub does not support direct internal-to-public issue transfer.
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 cerulion-inc/cerulion, 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 cerulion-inc/cerulion acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
cerulion-inc/cerulion has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 29.9 places cerulion-inc/cerulion in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
cerulion-inc/cerulion does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for cerulion-inc/cerulion 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.