Open-source TypeScript framework for building durable, resumable workflows. Supports Node.js and Bun.
C-Rank Grade: B (Solid) - 44/100
External PR Merge Rate: 68%
Response Time: 8d
First Timer Success: 50%
openworkflowdev/openworkflow has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in openworkflowdev/openworkflow respond to incoming external pull requests in approximately 201.6 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 44.1 places openworkflowdev/openworkflow in the B tier.
The external contributor pull request merge rate for openworkflowdev/openworkflow is 68.2%, based on public PR activity from non-core contributors.
openworkflowdev/openworkflow currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source TypeScript framework for building durable, resumable workflows. Supports Node.js and Bun.
Active TypeScript repository in openworkflowdev/openworkflow with ongoing community development and issue triage.
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/openworkflowdev/openworkflow?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~131 hours (85% approval). Large PRs (>500 lines) take ~968 hours (31% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in TypeScript.
Make CommonMark more friendly for Japanese/Chinese/Korean (CommonMark next specification draft)—plugins & patched packages
Open-source AI video workbench. Bring any model or your local ComfyUI, and let Claude Code / Codex / Cursor direct it over MCP — storyboard, references, generation, editable first cut on a real timeline. Local-first: projects, prompts, and keys stay on your machine. No account, no telemetry.
A platform to build useful communities that aim to tackle global problems
Is your feature request related to a problem? Please describe. Debugging workflows steps is hard. Specially when we want to know what steps are taking long time or failing. Describe the solution you'd like Create a workflow run detailed view, where we could see what step started at what time, and how long it took to complete. Inngest.js example below: Describe alternatives you've considered Additional context I can take care of this as a first contribution. I am not sure the cli / backend can provide the necessary information already. If it can't I will also need to implement this.
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 openworkflowdev/openworkflow, 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 openworkflowdev/openworkflow acknowledge new external contributions in approximately 8 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 68.2% were successfully merged into the primary branch.
openworkflowdev/openworkflow has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 days+. 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 44.1 places openworkflowdev/openworkflow in the Solid tier.
The external pull request merge rate is 68.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, openworkflowdev/openworkflow 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 openworkflowdev/openworkflow 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.