Wanaku Governed Action Proxy for AI Agents
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 86%
Response Time: 2d
First Timer Success: 57%
wanaku-ai/wanaku has a recorded first-timer success rate of 57.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in wanaku-ai/wanaku respond to incoming external pull requests in approximately 55.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 67.3 places wanaku-ai/wanaku in the A tier.
The external contributor pull request merge rate for wanaku-ai/wanaku is 86.4%, based on public PR activity from non-core contributors.
wanaku-ai/wanaku currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in wanaku-ai/wanaku. Prompt code reviews with positive guidance for new contributors.
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/wanaku-ai/wanaku?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~36 hours (96% approval). Large PRs (>500 lines) take ~268 hours (39% approval). Keep your diff compact for rapid review.
Description PR #2031 bumps `utoipa` from 5.5.0 to 6.0.0. This is a major version bump and a breaking change that requires code updates to adopt the new OpenAPI macro/annotation API before the Dependabot PR can be merged. Expected Behavior The codebase compiles and all tests pass with utoipa 6.0.0. Additional Context Dependabot PR: #2031 (branch: `dependabot/cargo/utoipa-6.0.0`)
Description PR #2077 bumps `zip` from 2.4.2 to 8.6.0. This is a major version bump and a breaking change that requires code updates before the Dependabot PR can be merged. Expected Behavior The codebase compiles and all tests pass with zip 8.6.0. Additional Context Dependabot PR: #2077 (branch: `dependabot/cargo/zip-8.6.0`)
Description The Plugin Configure Services modal (`PluginConfigModal`) accepts any free-text value for each service target URL. The placeholder text (`e.g. http://localhost:8080\`) hints at the expected format, but there is no validation to prevent users from entering an invalid address. Submitting a malformed URL will silently pass through to the backend and cause a confusing runtime error later. Input should be restricted to valid HTTP or HTTPS addresses in the form `http(s)://:`. Expected Behavior Each service target `TextInput` validates the entered value against a valid HTTP/HTTPS URL pattern (e.g. `^https?://[^/]+(:\d+)?(/.*)?$`). If the value is invalid, an inline `invalid` state is shown on the `TextInput` with a descriptive helper message (e.g. "Must be a valid HTTP or HTTPS address, e.g. http://localhost:8080"). The Save Configuration primary button is disabled while any field contains an invalid URL. Empty fields (optional services) are not flagged as invalid — only non-em
Description The Docker Compose getting-started guide does not work when authentication is enabled. The guide must provide a reliable, end-to-end workflow for authenticated local deployments. Scope Document the distinct roles of admin-cli and mcp-client. Use wanaku and wanaku-keycloak-admin in the guides where applicable, instead of curl. Fix CLI output so token refresh commands emit only token data to standard output. Log messages must not corrupt exported token values. Verify the documented Docker Compose authentication workflow from a clean environment. Link or coordinate with related issue #2026, which tracks the logout failure. Expected Behavior A user can follow the authenticated Docker Compose getting-started guide without manual corrections or ambiguous tool choices. Actual Behavior The current guide and CLI behavior cause authentication setup and token handling failures.
Description Update documentation that uses curl for Wanaku management API operations. Prefer equivalent wanaku CLI commands where the CLI supports the operation. Update the getting-started guide to direct users to the Wanaku CLI download page before it uses CLI commands. Keep curl examples for MCP protocol requests, authentication token retrieval, upstream MCP checks, and other operations that the CLI does not support. Scope Review at least these documents: docs/getting-started.md docs/management-api.md docs/migration-from-classic.md docs/action-policies.md docs/architecture.md docs/evaluator-engine.md docs/features.md Use the existing CLI documentation examples as the command reference. Preserve API examples when there is no CLI equivalent. Acceptance Criteria The getting-started guide links users to the Wanaku CLI download page and includes the CLI installation and verification steps before CLI usage. Management API curl examples have equivalent wanaku CLI commands where available
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 wanaku-ai/wanaku, 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 wanaku-ai/wanaku acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.4% were successfully merged into the primary branch.
wanaku-ai/wanaku has a recorded first-timer success rate of 57.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 67.3 places wanaku-ai/wanaku in the Welcoming tier.
The external pull request merge rate is 86.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, wanaku-ai/wanaku 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 wanaku-ai/wanaku 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.