GoClaw - GoClaw is OpenClaw rebuilt in Go — with multi-tenant isolation, 5-layer security, and native concurrency. Deploy AI agent teams at scale without compromising on safety.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 62%
Response Time: -
First Timer Success: 41%
nextlevelbuilder/goclaw has a recorded first-timer success rate of 41.2%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in nextlevelbuilder/goclaw respond to incoming external pull requests in approximately 0.0 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 65.6 places nextlevelbuilder/goclaw in the A tier.
The external contributor pull request merge rate for nextlevelbuilder/goclaw is 62.1%, based on public PR activity from non-core contributors.
nextlevelbuilder/goclaw currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (61% critical review signals). Ensure PRs strictly follow guidelines before requesting review in nextlevelbuilder/goclaw.
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/nextlevelbuilder/goclaw?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (78% approval). Large PRs (>500 lines) take ~115 hours (28% approval). Keep your diff compact for rapid review.
[Bug] Xoá agent thất bại — unique index uq_vault_docs_agent_team_scope_path va chạm khi orphan vault docs sang scope shared Mô tả vấn đề Khi xoá một agent có vault documents, RPC agents.delete trả về lỗi 500: Error deleting agent: gateway error (500): failed to delete agent: internal error Log gateway: level=ERROR msg=agents.delete id=019e5e1c-…-18d288d10167 error="ERROR: duplicate key value violates unique constraint \"uq_vault_docs_agent_team_scope_path\" (SQLSTATE 23505)" Agent không thể xoá được bằng bất kỳ đường nào (Web UI, CLI goclaw agent delete --force, RPC). Toàn bộ transaction bị rollback. Đây là hệ quả trực tiếp của cách fix #1077 (orphan vault docs sang scope='shared' thay vì personal). Fix đó giải quyết được CHECK constraint 23514, nhưng đẩy mọi doc mồ côi vào chung một không gian khoá và tạo ra va chạm UNIQUE 23505. Nguyên nhân gốc Ba thay đổi trong migrat
Summary ValidateArgs() in internal/mcp/validation.go flags arguments containing -c as a dangerous pattern. This produces false positives for legitimate package names like clickup-cli, where -cli starts with the -c substring. Steps to Reproduce Configure an MCP server with command npx and args ["@nick.bester/clickup-cli", "mcp", "serve"] Attempt to start the MCP server Error: invalid args: arg[0] contains dangerous pattern "-c" Root Cause The dangerous pattern check appears to do a substring/prefix match for -c (intended to block -c as a code execution flag for interpreters like python -c, ruby -c, etc.). However, it matches any argument containing the -c substring, including: clickup-cli (contains -cli which starts with -c) Any npm package with -c* in the name Expected Behavior The -c check should only match when -c appears as a standalone flag (e.g. exact match -c, or followed by a space/end-of-string), not as a substring within package names or paths. Workaround Use a Python wrap
Problem Provider catalog currently hard-codes known vendors (Anthropic, OpenAI, DashScope, Claude CLI, ACP, Codex). Users running self-hosted or niche OpenAI-compatible gateways (vLLM, LM Studio, LiteLLM, Ollama proxy, OpenRouter, Together, Groq, Fireworks, local inference) cannot register them without either (a) hijacking the openai type and mismatching defaults, or (b) shipping a new provider_type per vendor. Neither scales. Goal Introduce a neutral custom provider_type that treats any endpoint as OpenAI chat-completions compatible, so ops teams can onboard new backends via config/UI without code changes. Scope In scope Backend: accept provider_type = "custom" in provider store + HTTP validation. Routing: resolve custom through the existing OpenAI-compatible adapter (HTTP + SSE). Model listing: expose /v1/models passthrough for custom endpoints. UI: add "Custom Provider" entry in provider dropdown with i18n (en/vi/zh). Tests: unit + integration contract coverage. Out of scope Non-
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 nextlevelbuilder/goclaw, 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 nextlevelbuilder/goclaw acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 62.1% were successfully merged into the primary branch.
nextlevelbuilder/goclaw has a recorded first-timer success rate of 41.2%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 65.6 places nextlevelbuilder/goclaw in the Welcoming tier.
The external pull request merge rate is 62.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, nextlevelbuilder/goclaw 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 nextlevelbuilder/goclaw 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.