Design, Test and Document APIs in plain Markdown. Compose Requests with API blocks. Reuse, Replace & Version everything just like code. Offline, Truly Git Native, No Lock-in.
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 78%
Response Time: 8h
First Timer Success: 67%
VoidenHQ/voiden has a recorded first-timer success rate of 66.7%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in VoidenHQ/voiden respond to incoming external pull requests in approximately 8.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 74.2 places VoidenHQ/voiden in the S tier.
The external contributor pull request merge rate for VoidenHQ/voiden is 78.2%, based on public PR activity from non-core contributors.
VoidenHQ/voiden currently has 22 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Design, Test and Document APIs in plain Markdown. Compose Requests with API blocks. Reuse, Replace & Version everything just like code. Offline, Truly Git Native, No Lock-in.
Highly welcoming maintainers in VoidenHQ/voiden. Prompt code reviews with positive guidance for new contributors.
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/VoidenHQ/voiden?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 13:00 to 17:00 UTC (13:00 - 17: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 ~5 hours (96% approval). Large PRs (>500 lines) take ~40 hours (35% 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.
No repository description available.
Build and deploy AI Agents on Cloudflare
AI agents, automations and apps that run your operations. Model agnostic.
Description After working in the terminal with AI agent for a while, scrolling down causes the text in the terminal input area to start overlapping, making it difficult to read and use. Steps to Reproduce Open Voiden. Open the terminal and start working with AI agent . Continue working in the terminal for some time. Scroll down through the terminal output. Observe the text in the input area. Actual Behavior The text in the terminal input area starts overlapping when scrolling down. Expected Behavior The input text should remain properly aligned and readable while scrolling, without any overlap. Screen.Recording.2026-08-20.at.11.20.47.AM.mov
Split out from #513 so that ticket can stay focused on what's already landed. These are the categories/items from #513 that are being deferred — not started, no design decisions made yet. Assertions Parse the response body to help users build assertions Add autocomplete based on the response structure (Already done in #513: better guidance when assertions fail, showing available operators without typing first, and a complete list of assertion commands — see that issue for details.) Feature Suggestions Add one-click assertion generation directly from the response Automatically convert response values into assertions (Scoped but not started — flagged as Large effort, not a quick fix: the response body currently renders as raw text in a CodeMirror instance (ResponseBodyNode.tsx), so there's no structured/clickable JSON to hang a "+" affordance off — this needs a net-new JSON tree view component with per-field path computation. The response viewer is also a separate, read-o
I have some suggestion for the stitch runner. We get normal list of endpoint with green and red dots. Green for pass and red for fail. There should be some way to filter them out as well to only view the failed ones. Can we also provide the text or md report as well. With more detailed observation on error and status code etc. Example like table with status code how many endpoint got what status codes How many api get 200 status code but being considered failed because of assertions.
When I save a file using Command + S, the folders that are currently expanded in the file explorer automatically collapse. This interrupts the file navigation flow and forces the user to expand the folders again. Screen.Recording.2026-08-12.at.3.37.16.PM.mov
Summary Create a plugin that detects changes in API response structures between executions. Use Cases Identify breaking API changes. Validate API stability. Monitor response schema evolution. Catch regressions before deployment. Proposed Features Compare response schemas between runs. Highlight added, removed, and modified fields. Ignore configurable fields. Export comparison reports. Support JSON and XML responses. Optional CI integration. Benefits Detects breaking changes early. Improves API reliability. Helps maintain backward compatibility.
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 VoidenHQ/voiden, 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 VoidenHQ/voiden acknowledge new external contributions in approximately 8 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.2% were successfully merged into the primary branch.
VoidenHQ/voiden has a recorded first-timer success rate of 66.7%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 74.2 places VoidenHQ/voiden in the Elite tier.
The external pull request merge rate is 78.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, VoidenHQ/voiden currently has 22 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for VoidenHQ/voiden 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.