Source-available, self-hosted AI agent workspace for small businesses and lean teams — with BYOK, workflows, tools, and human approvals.
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 100%
Response Time: -
First Timer Success: 100%
manor-os/manor-ai has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in manor-os/manor-ai 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 51.7 places manor-os/manor-ai in the B tier.
The external contributor pull request merge rate for manor-os/manor-ai is 100.0%, based on public PR activity from non-core contributors.
manor-os/manor-ai currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in manor-os/manor-ai. Reviews community pull requests with focus on project quality.
Discussions in manor-os/manor-ai 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/manor-os/manor-ai?utm_source=github&utm_medium=badge)
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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 19:00 to 23:00 UTC (19:00 - 23:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (45% approval). Keep your diff compact for rapid review.
Why apps/web/src/pages/Activity.tsx already translates the page title, empty state, and tab labels, but activity badges still render the raw backend event key such as task, document, or user. The file also contains a stale TODO about localizing the event tabs. This is a small frontend improvement that makes the Activity page consistent in English, Chinese, and Spanish without changing the API. Scope Add Activity event-label translation keys for: task document user goal agent chat system Add the keys to: apps/web/src/lib/i18n/en.ts apps/web/src/lib/i18n/zh.ts apps/web/src/lib/i18n/es.ts Update apps/web/src/pages/Activity.tsx so: tabs use the Activity-specific event-label mapping; badges show the localized label instead of the raw event key; unknown event types use the existing page.activity.event_fallback translation; the stale localization TODO is removed. Add a focused Node source test, for example apps/web/scripts/activity-i18n.test.mjs, that verifies the mapping is used an
Why The current Quick Start gets a self-hosted operator to a running stack and a model smoke test, while the Agents concept page explains the model at a high level. New users still need one concrete, end-to-end walkthrough for creating and testing their first agent. Scope Add a self-hosted guide at docs-site/docs/guides/first-agent.md and link it from the Learn section of docs-site/sidebars.js. The guide should cover: Prerequisites: a running local stack, the demo account, and a configured BYOK model provider. Creating an agent with a clear name and a short, auditable instruction. Selecting the configured model and saving the agent. Running a simple prompt or task that does not require external credentials. Explaining the expected result and where to inspect execution evidence. Troubleshooting the two most likely failures: no model response and insufficient tool permission. A short Where to go next section linking to skills/tools and HITL governance. Also add a link to the new walkth
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 manor-os/manor-ai, 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 manor-os/manor-ai acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
manor-os/manor-ai has a recorded first-timer success rate of 100.0%. Repositories ranked Solid 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 51.7 places manor-os/manor-ai in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, manor-os/manor-ai 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 manor-os/manor-ai 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.