🪓 An orchestration engine for background tasks, AI agents, and durable workflows
C-Rank Grade: A (Welcoming) - 63/100
External PR Merge Rate: 73%
Response Time: -
First Timer Success: 57%
hatchet-dev/hatchet 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 hatchet-dev/hatchet 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 63.1 places hatchet-dev/hatchet in the A tier.
The external contributor pull request merge rate for hatchet-dev/hatchet is 73.5%, based on public PR activity from non-core contributors.
hatchet-dev/hatchet currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in hatchet-dev/hatchet. Maintains strict focus on technical quality and test standards.
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/hatchet-dev/hatchet?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (92% approval). Large PRs (>500 lines) take ~115 hours (33% approval). Keep your diff compact for rapid review.
Describe the issue I'm not sure if this is working as intended. When we filter by metadata, we don't have a way to filter runs using OR when the keys are the same. For example, I want to filter runs that have test_id being either A or B. As of now, B overwrites A and only those with test_id = B are filtered. Environment SDK: [e.g. TypeScript v1.2.3]: Python Engine: [Cloud or Self-hosted v1.5.0]: Self-hosted v0.95.3 Expected behavior What did you expect to happen instead? We should be able to see all runs associated with test_id = A and test_id = B. Code to Reproduce, Logs, or Screenshots Included above Additional context 🤖 AI Disclosure I acknowledge that an LLM was used in the creation of this Issue, in accordance with Hatchet's AI_POLICY.md. I didn't use AI to write this issue. Details: [e.g. re-creation steps, initial diagnosis]
Describe the issue When default retries are set using TaskDefaults(retries=3), you can't disable them for a specific task, as the @task decorator has retries=0 as default value (instead of None or some other sentinel value) Environment SDK: Python 1.37.2 Engine: irrelevant Expected behavior You can disable retries on individual tasks Code to Reproduce, Logs, or Screenshots In this example, no_retry_task will have retries=3 some_wf = hatchet.workflow( name="SomeWF", task_defaults=TaskDefaults( retries=3 ), ) @some_wf.task(retries=0) def no_retry_task(...): ... Additional context The code handling defaults is here https://github.com/hatchet-dev/hatchet/blob/main/sdks/python/hatchet_sdk/runnables/workflow.py#L139-L143 🤖 AI Disclosure This was written entirely by hand
Describe the issue When the application is being used in dark mode, the Support Chat widget opens in light mode instead of inheriting the current application theme. Step to produce: Open Hatchet cloud dashboard with dark mode enabled. Navigate to any page. Open the Support Chat from the sidebar. Observe the chat widget appearance. Environment SDK: [e.g. TypeScript v1.2.3] Engine: [Cloud or Self-hosted v1.5.0] Expected behavior The Support Chat should follow the application's active theme and render in dark mode when the dashboard is using dark mode. Code to Reproduce, Logs, or Screenshots . 🤖 AI Disclosure I acknowledge that an LLM was used in the creation of this Issue, in accordance with Hatchet's AI_POLICY.md. Details: [e.g. re-creation steps, initial diagnosis]
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 hatchet-dev/hatchet, 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 hatchet-dev/hatchet acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.5% were successfully merged into the primary branch.
hatchet-dev/hatchet 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 ~-. 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 63.1 places hatchet-dev/hatchet in the Welcoming tier.
The external pull request merge rate is 73.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, hatchet-dev/hatchet 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 hatchet-dev/hatchet 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.