Meet Coco. A superintelligent agent framework powered by an advisory board of 389 world-class minds. Scale your AI assistant into a complete engineering department with 142 skills, 277 commands, and persistent state. Universal compatibility. Local privacy. Free and open source.
C-Rank Grade: B (Solid) - 77/100
External PR Merge Rate: 93%
Response Time: 2h
First Timer Success: 50%
coco-research/coco has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in coco-research/coco respond to incoming external pull requests in approximately 1.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 76.6 places coco-research/coco in the B tier.
The external contributor pull request merge rate for coco-research/coco is 93.1%, based on public PR activity from non-core contributors.
coco-research/coco currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Meet Coco. A superintelligent agent framework powered by an advisory board of 389 world-class minds. Scale your AI assistant into a complete engineering department with 142 skills, 277 commands, and persistent state. Universal compatibility. Local privacy. Free and open source.
Growing JavaScript project in coco-research/coco 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/coco-research/coco?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 14:00 to 18:00 UTC (14:00 - 18: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 ~4 hours (96% approval). Large PRs (>500 lines) take ~9 hours (42% 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 JavaScript.
The web end of seafile server.
Wazuh - Project documentation
ComfyTV — the canvas-based app that truly belongs to ComfyUI.
Goal Add a zed adapter so Coco installs into the Zed editor's AI/agent configuration. Files involved adapters/zed/manifest.json (new) adapters/zed/install.sh (new) — wire skills/commands/rules into Zed's config (or emit an AGENTS.md if Zed consumes one) adapters/zed/README.md (new) install.sh — optional detect_adapter() heuristic for Zed Acceptance criteria bash install.sh --adapter zed installs without error into Zed's config location manifest.json validates; README documents the target paths and limitations CI passes (frontmatter linter, manifest validator, install script syntax check) README System Compatibility table gains a Zed row Hints Start from adapters/generic (AGENTS.md producer) or adapters/cursor. Adding an adapter: CONTRIBUTING.md
Goal Strengthen evidence sourcing for the subset of Superintelligence personas that do not yet clear the strict anti-fabrication validator, so the full 389-persona board passes validate_persona.py cleanly. Background The 6 newer teams (Finance, Trading, Risk & Compliance, Strategy, Data & Analytics, GTM) shipped with roughly 155/204 personas passing the strict gate. The remainder fall short on quotas the validator enforces: at least 4 live (non-404) cited evidence URLs every public_stance carrying a real evidence_url at least 2 verified signals within the last 12 months (or persistent_signals for archetype/historical figures) no fabricated quotes; a valid home team These are link-rot / under-quota cases — not fabrications — but they should be brought up to standard. How to help Run the validator to list sub-threshold personas: python3 systems/superintelligence/<team>/scripts/validate_persona.py (or the team's validate_all_generic.py). Pick a persona, research current public sour
Goal Add a coco doctor health-check that diagnoses a Coco install and prints a clear pass/fail report. New users currently have no single command to confirm everything wired up correctly. What it should check Required tools present: git, bash, python3 (and node for the npm CLI) Detected IDE/adapter (~/.claude, ~/.cursor, VS Code, Codex) Symlinks resolve (no dangling links into the repo) Installed bundles (gsd / brain / team / superintelligence) and their asset counts For Superintelligence: that SI commands were generated (per-team + meta) Installed version + whether an update is available (reuse scripts/check-update.sh) Files involved scripts/doctor.sh (new), or a doctor subcommand in bin/coco.js Wire a mention into install.sh output and the README "Staying Current" section Acceptance criteria bash scripts/doctor.sh (or coco doctor) prints a readable report with ✓/✗ per check Exit code non-zero when a hard requirement is missing Offline-safe; no telemetry CI passes (instal
Goal Add an antigravity IDE adapter so Coco artifacts install into Google's Antigravity editor. The README's System Compatibility table lists Antigravity as Planned for v0.2 — this issue tracks building it. Files involved adapters/antigravity/manifest.json (new) — mirror an existing adapter's manifest adapters/antigravity/install.sh (new) — link/compile skills, commands, agents, rules into Antigravity's config location adapters/antigravity/README.md (new) install.sh — detect_adapter() may add an Antigravity heuristic Reference adapters/cursor/ and adapters/vscode-continue/ are the closest patterns. The generic adapter (AGENTS.md producer) is a good fallback model if Antigravity supports AGENTS.md. Acceptance criteria bash install.sh --adapter antigravity installs without error Skills, commands, agents, and rules are wired into the correct Antigravity location manifest.json validates; README documents the target paths CI passes (frontmatter linter, manifest validator, ins
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 coco-research/coco, 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 coco-research/coco acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 93.1% were successfully merged into the primary branch.
coco-research/coco has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 hours. 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 76.6 places coco-research/coco in the Solid tier.
The external pull request merge rate is 93.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, coco-research/coco currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for coco-research/coco 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.