An AI-powered task-management system you can drop into Cursor, Lovable, Windsurf, Roo, and others.
C-Rank Grade: D (Risky) - 21/100
External PR Merge Rate: -
Response Time: 23h
First Timer Success: -
eyaltoledano/claude-task-master has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in eyaltoledano/claude-task-master respond to incoming external pull requests in approximately 23.4 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 21.3 places eyaltoledano/claude-task-master in the D tier.
The external contributor pull request merge rate for eyaltoledano/claude-task-master is 0.0%, based on public PR activity from non-core contributors.
eyaltoledano/claude-task-master currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
An AI-powered task-management system you can drop into Cursor, Lovable, Windsurf, Roo, and others.
Collaborative maintainer environment in eyaltoledano/claude-task-master. Reviews community pull requests with focus on project quality.
Discussions in eyaltoledano/claude-task-master 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/eyaltoledano/claude-task-master?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~15 hours (81% approval). Large PRs (>500 lines) take ~112 hours (29% approval). Keep your diff compact for rapid review.
Problem Several warning and error messages reference npm install -g @anthropic-ai/claude-code as the install method for Claude Code CLI. Claude Code now distributes as a native binary and the primary install method is via the install script or platform package managers. Affected Locations claude-task-master: src/ai-providers/claude-code.js:88 - CLI detection warning src/ai-providers/claude-code.js:150 - CLI initialization error packages/tm-core/src/modules/loop/services/loop.service.ts:589 - Loop service error docs/examples/claude-code-usage.md:63-65 - Documentation ai-sdk-provider-claude-code (separate repo): examples/README.md:12 examples/basic-usage.ts:61 examples/check-cli.ts:33,39 Current Message Claude Code CLI not detected. Install it with: npm install -g @anthropic-ai/claude-code Expected Install instructions should reference the current primary install method and/or link to official documentation. The npm install method still works but is no longer the primary distributio
Summary Follow-up to #1594. The current help sync test only checks if commands exist in help documentation, not if their subcommands/options are correctly documented. Problem PR #1593 fixed outdated help documentation where: tags showed old commands (add-tag, use-tag) instead of new subcommand structure (tags add, tags use) list was missing new options (--watch, --ready, --blocking) The test in #1595 wouldn't catch these issues because it only verifies command existence. Proposed Enhancement Add verification that: tags subcommands are documented (tags add, tags use, tags remove, tags rename, tags copy, tags list) Key command options are documented (e.g., list shows --watch, --ready, --blocking) Dependencies Requires #1593 to be merged first (or branch from it) Related #1588 - Original help outdated issue #1593 - Fix for outdated help #1594 - Original test issue #1595 - Basic help sync test PR
Problem Statement The help documentation in scripts/modules/ui.js (displayHelp()) can become outdated when commands are added, removed, or modified. This was discovered in #1588 where the tag commands and list options were out of sync with the actual implementations. Proposed Solution Add a lint rule or test that fails when help documentation doesn't match the actual command implementations. Approaches to Consider Command registry comparison test Extract command names/options from apps/cli/src/commands/*.ts files Compare against entries in displayHelp() Fail if commands exist in CLI but not in help (or vice versa) Single source of truth refactor Define command metadata (name, args, description) in one place Have both Commander setup and help display read from the same source Eliminates drift by design Snapshot test with review requirement Snapshot the help output Require explicit update when commands change Forces developer to consciously update help Suggested Implementat
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 eyaltoledano/claude-task-master, 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 eyaltoledano/claude-task-master acknowledge new external contributions in approximately 23 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
eyaltoledano/claude-task-master has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~23 hours. 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 21.3 places eyaltoledano/claude-task-master in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, eyaltoledano/claude-task-master currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for eyaltoledano/claude-task-master 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.