First-tree routes work to the right agent, gives it the same context your team has, and loops humans in only when the rules say so. Lives in your GitHub. Open source.
C-Rank Grade: S (Elite) - 68/100
External PR Merge Rate: 72%
Response Time: -
First Timer Success: 71%
first-tree-ai/first-tree has a recorded first-timer success rate of 71.4%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in first-tree-ai/first-tree 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.4 places first-tree-ai/first-tree in the S tier.
The external contributor pull request merge rate for first-tree-ai/first-tree is 71.8%, based on public PR activity from non-core contributors.
first-tree-ai/first-tree currently has 18 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
First-tree routes work to the right agent, gives it the same context your team has, and loops humans in only when the rules say so. Lives in your GitHub. Open source.
Strict review standards in first-tree-ai/first-tree. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in first-tree-ai/first-tree 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/first-tree-ai/first-tree?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (90% approval). Large PRs (>500 lines) take ~115 hours (32% approval). Keep your diff compact for rapid review.
PERF-062：客户端接受最大达到 WebSocket 库默认值 100 MiB 的帧 中文 描述： 客户端没有配置 maxPayload，因此 ws 允许约 100 MiB 的帧。随后，完整帧还会被转换为字符串并解析为 JSON，产生额外的大块内存分配，而服务端协议上限实际上只有 64 KiB。 严重性： 中等（Medium） 文件位置： packages/client/package.json:38、packages/client/src/client-connection.ts:1142、packages/client/src/client-connection.ts:1227-1232、packages/server/src/app.ts:340-344 预计修复时间： 0.5-1 天 建议修复方向： 设置与协议一致的明确客户端上限，在转换帧之前拒绝超限数据，并增加集成测试以证明守护进程在收到超大帧后仍保持健康。 English Description: The client does not configure maxPayload, so ws permits approximately 100 MiB. The complete frame is then converted to a string and parsed as JSON, creating additional large allocations even though the server-side protoco
PERF-058：客户端更新循环保护状态不具备崩溃原子性 中文 描述： 尽管代码注释声称这里采用原子写入，实际实现却会直接截断并写入目标文件。进程崩溃或断电可能导致保护状态文件损坏或变空，从而使同一个有问题的更新再次触发重复重启尝试。 严重性： 中等（Medium） 文件位置： apps/cli/src/core/update-state.ts:49-76 预计修复时间： 2-4 小时 建议修复方向： 先写入一个设置了正确权限的临时文件，按需执行 flush/fsync，再通过 rename 原子替换目标文件；同时测试在每个写入阶段发生中断时的行为。 English Description: Despite the atomic-write comment, the file is written by truncating the destination directly. A crash or power loss can corrupt/empty the guard and allow repeated restart attempts for the same broken update. Severity: Medium Locations: apps/cli/src/core/update-state.ts:49-76 Estimated remediation: 2-4 hours Recommended
English Severity: Medium Location: packages/server/src/api/healthz.ts:10-15 Estimated remediation: 2-4 hours Description: /healthz explicitly disables rate limiting and executes SELECT 1 per request. Public traffic or overly aggressive probes can create unlimited database round trips, including when the database is already unhealthy. Recommended direction: Split process liveness from database readiness, restrict readiness at ingress or give it an independent cheap limit/cache, and tune probe cadence. 中文：公共健康检查不受限地查询 PostgreSQL 严重性： 中 位置： packages/server/src/api/healthz.ts:10-15 预计修复时间： 2-4 小时 描述： /healthz 显式禁用了速率限制，并且每次请求都会执行 SELECT 1。公共流量或过于激进的探针可能造成不受限制的数据库往返，即使数据库本身已经处于不健康状态也会如此。 建议方向： 将进程存活检查与数据库就绪检查拆分开；在入口层限制就绪
English Severity: Medium Location: packages/server/src/api/agent-usage.ts:18-47, packages/server/src/api/orgs/usage.ts:15-22, packages/server/src/services/usage.ts:95-187, packages/server/src/services/usage.ts:317-329 Estimated remediation: 0.5 day Description: from/to only need to parse; there is no ordering check, maximum span, or earliest boundary. An authenticated member can repeatedly force full-history session-event JSONB aggregates and index scans. Recommended direction: Enforce strict timestamps, from < to, a configurable maximum window, and a privileged offline export path for larger ranges. 中文：使用量聚合允许无上限的历史时间窗口 严重性： 中 位置： packages/server/src/api/agent-usage.ts:18-47、packages/server/src/api/orgs/usage.ts:15-22、packages/server/src/services/usage.ts:95-187、packages/server/src/services/usage.ts:317-329 预计修复时间： 0.5 天 描述： from 和 to 只需能够解析即可；系统没有检查二者的先后顺
English PERF-048 - Document export is an unbounded sequential N+1 operation Description: All document summaries accumulate in memory, then each full document is fetched sequentially and written synchronously. Export duration grows with one network round trip per document while memory retains the complete summary set. Severity: Medium Locations: apps/cli/src/commands/doc/export.ts:37-48 Estimated remediation: 1 day Recommended direction: Stream paginated summaries and files with small bounded fetch/write concurrency and resumable progress. 中文 PERF-048 - 文档导出是无界且串行的 N+1 操作 描述： 所有文档摘要都会先累积在内存中，随后系统会逐个串行获取完整文档，并同步写入文件。每份文档都会增加一次网络往返，因此导出时间会随文档数增长；与此同时，内存始终保留完整的摘要集合。 严重性： 中等 文件位置： apps/cli/src/commands/doc/export.ts:37-48 预计修复时间： 1 天 建议
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 first-tree-ai/first-tree, 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 first-tree-ai/first-tree acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 71.8% were successfully merged into the primary branch.
first-tree-ai/first-tree has a recorded first-timer success rate of 71.4%. Repositories ranked Elite 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.4 places first-tree-ai/first-tree in the Elite tier.
The external pull request merge rate is 71.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, first-tree-ai/first-tree currently has 18 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for first-tree-ai/first-tree 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.