Production-grade platform for building agentic IM bots - 生产级多平台智能机器人开发平台/ Agent、知识库编排、插件系统 / Bots for Discord / Slack / LINE / Telegram / WeChat(企业微信, 企微智能机器人, 公众号) / 飞书 / 钉钉 / QQ / Matrix e.g. Integrated with ChatGPT(GPT), DeepSeek, Dify, n8n, Langflow, Coze, Claude, Gemini, GLM, Ollama, SiliconFlow, Moonshot, openclaw / hermes agent, deerflow
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 76%
Response Time: -
First Timer Success: 82%
langbot-app/LangBot has a recorded first-timer success rate of 82.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in langbot-app/LangBot 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 68.8 places langbot-app/LangBot in the A tier.
The external contributor pull request merge rate for langbot-app/LangBot is 76.3%, based on public PR activity from non-core contributors.
langbot-app/LangBot currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Production-grade platform for building agentic IM bots - 生产级多平台智能机器人开发平台/ Agent、知识库编排、插件系统 / Bots for Discord / Slack / LINE / Telegram / WeChat(企业微信, 企微智能机器人, 公众号) / 飞书 / 钉钉 / QQ / Matrix e.g. Integrated with ChatGPT(GPT), DeepSeek, Dify, n8n, Langflow, Coze, Claude, Gemini, GLM, Ollama, SiliconFlow, Moonshot, openclaw / hermes agent, deerflow
Collaborative maintainer environment in langbot-app/LangBot. Reviews community pull requests with focus on project quality.
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/langbot-app/LangBot?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 09:00 UTC (09:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (95% approval). Large PRs (>500 lines) take ~115 hours (34% approval). Keep your diff compact for rapid review.
Summary Remote MCP servers that use OAuth 2.0 (the MCP "Authorization" spec with WWW-Authenticate: Bearer realm="OAuth" + resource_metadata) cannot be connected from LangBot. The SSE/HTTP MCP connector only supports static headers, so any OAuth-protected hosted server returns 401/403 on connect, and the install UI gives the user no way to complete an authorization flow. This affects several popular hosted MCP servers now listed on LangBot Space (Linear, Vercel, Cloudflare, and a growing number of first-party hosted servers that are moving to OAuth). Steps to reproduce Add an SSE MCP server pointing at https://mcp.linear.app/sse (or install "Linear" from the Space marketplace). Enable it / connect. Connection fails with 401 Unauthorized. Root cause The MCP loader builds the transport from static config only: src/langbot/pkg/provider/tools/loaders/mcp.py SSE: sse_client(url, headers=server_config.get('headers', {}), ...) HTTP: streamable_http_client(url, http_client=httpx.AsyncClient
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 langbot-app/LangBot, 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 langbot-app/LangBot acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 76.3% were successfully merged into the primary branch.
langbot-app/LangBot has a recorded first-timer success rate of 82.4%. 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 68.8 places langbot-app/LangBot in the Welcoming tier.
The external pull request merge rate is 76.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, langbot-app/LangBot 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 langbot-app/LangBot 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.