Aspire is the tool for code-first, extensible, observable dev and deploy.
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 66%
Response Time: -
First Timer Success: 48%
microsoft/aspire has a recorded first-timer success rate of 48.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in microsoft/aspire 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.9 places microsoft/aspire in the A tier.
The external contributor pull request merge rate for microsoft/aspire is 66.4%, based on public PR activity from non-core contributors.
microsoft/aspire does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in microsoft/aspire. 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/microsoft/aspire?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (83% approval). Large PRs (>500 lines) take ~115 hours (30% approval). Keep your diff compact for rapid review.
Is there an existing issue for this? I have searched the existing issues Is your feature request related to a problem? Please describe the problem. When a workspace contains only one AppHost, the Aspire pane still requires the user to expand it before its actions are visible. There is no ambiguity in this case, so the extra interaction hides the available AppHost actions unnecessarily. Describe the solution you'd like When AppHost discovery finds exactly one AppHost in the workspace, automatically expand that AppHost in the Aspire pane so all of its actions are immediately shown. Additional context This is part of #19405.
Is your feature request related to a problem? Please describe the problem. When AppHost start and stop operations are invoked from a git worktree, they are not aware that the checkout is a linked worktree. A start can conflict with an instance from the primary checkout or another worktree, and a stop can target the wrong running AppHost unless the caller manually supplies the correct isolation and project options. Describe the solution you'd like Make the AppHost start and stop operations detect the current git worktree. Starting from a linked worktree should automatically use isolated mode, while stopping should prefer or scope itself to the AppHost associated with that worktree. Explicit project or isolation arguments should continue to override inferred behavior. Additionally, an isolated property should be exposed via the tool so it is more discoverable to agents Additional context This would make concurrent agent and developer workflows safer without requiring every caller to unde
Is there an existing issue for this? I have searched the existing issues Describe the bug If timestamps are not enabled, the options menu on the Console page shouldn't show the UTC timestamps checkbox. Expected Behavior The UTC timestamps option should be hidden when timestamps are not being shown. Steps To Reproduce Open the dashboard Go to Console logs page Open filters in the top right. Exceptions (if any) No response Aspire doctor output Aspire Environment Check ======================== Aspire ⚠️ Aspire CLI version 13.5.0-preview.1.26405.1 (channel: daily) is out of date. Latest version is 13.5.0-preview.1.26405.2 (channel: prerelease) Run 'aspire update' to update Aspire CLI. ✅ Developer Control Plane (DCP) connection health checks succeeded AppHost ✅ AppHost version 13.5.0-preview.1.26405.1 (app\Trayport.Aspire.AppHost\Trayport.Aspire.AppHost.csproj) .NET SDK ✅ .NET 10.0.302 installed (x64) Container Runtime ✅ Docker v29.6.2:
Is there an existing issue for this? I have searched the existing issues Describe the bug In the New UI, the Capture paused message looks a bit weird to me. Expected Behavior I'd expect to either see it to the left of "Showing X structured logs", or for it to show up central on the whole page Steps To Reproduce Go to Structured logs page. Pause log capture Look at the "Capture paused" warning Exceptions (if any) No response Aspire doctor output No response Anything else? No response
Is there an existing issue for this? I have searched the existing issues Describe the bug Using the new UI in main, clicking on Filter brings up a history box with items that don't seem particularly relevant Expected Behavior I'm not sure that showing saved items for history is particularly useful - at least not without restricting the history to things specifically entered into aspire. Steps To Reproduce Go to "Structured Logs" page Click in the "Filter" box Exceptions (if any) No response Aspire doctor output Aspire Environment Check ======================== Aspire ⚠️ Aspire CLI version 13.5.0-preview.1.26405.1 (channel: daily) is out of date. Latest version is 13.5.0-preview.1.26405.2 (channel: prerelease) Run 'aspire update' to update Aspire CLI. ✅ Developer Control Plane (DCP) connection health checks succeeded AppHost ✅ AppHost version 13.5.0-preview.1.26405.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 microsoft/aspire, 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 microsoft/aspire acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.4% were successfully merged into the primary branch.
microsoft/aspire has a recorded first-timer success rate of 48.0%. 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.9 places microsoft/aspire in the Welcoming tier.
The external pull request merge rate is 66.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
microsoft/aspire does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for microsoft/aspire 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.