microsoft/aspire

Aspire is the tool for code-first, extensible, observable dev and deploy.

View on GitHub ↗Jump to charts ↓Open shareable report →

microsoft/aspire has 6k+ stars and 1k+ forks on GitHub, is written in C#, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 25 minutes ago
Added to GitGenius on September 10th, 2026
Created on September 25th, 2023
Open Issues & Pull Requests: 2,618 (+0)
GitHub issues: Enabled
Number of forks: 1,013
Total Stargazers: 6,371 (+0)
Total Subscribers: 83 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.9 hours
Mean response time: 17.8 days
90th percentile: 26.0 days
Tracked items: 788

Maintainer activity

18 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 65% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "area-dashboard" is answered fastest, typically in under an hour, while "ci-failure-cause" waits about 3 days. Almost all tracked open issues have seen activity in the last three months. Only 45% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 561
New in 7 days: 103
Closed in 7 days: 25
Avg open age: 52 days
Stale 30+ days: 56
Stale 90+ days: 0

Recent activity

Opened in 7 days: 86
Closed in 7 days: 22
Comments in 7 days: 85
Events in 7 days: 321

Top labels

  • triage:bot-seen (258)
  • needs-area-label (209)
  • agentic-workflows (188)
  • area-cli (143)
  • ci-failure-cause (143)
  • test-failure (110)
  • area-app-model (106)
  • area-vscode (104)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Aspire is a code-first orchestration and observability platform for .NET developers building distributed applications.

Aspire addresses the complexity of developing and deploying multi-service applications by letting developers define their entire application topology in code rather than through configuration files or manual setup. It provides a unified way to manage service dependencies, configure networking, and wire up observability across all components. The approach centers on a declarative model where developers describe their application structure using .NET, and Aspire handles the orchestration of local development environments and generates deployment artifacts for cloud platforms.

Aspire suits teams building microservices or multi-container applications who want to keep infrastructure concerns close to their application code. It is particularly valuable for developers who need consistent observability across development and production environments without separate tooling. The platform integrates with standard .NET tooling and works with services written in languages beyond C#, making it applicable to polyglot teams. Developers should adopt Aspire if they prefer managing application topology programmatically and want built-in support for tracing, metrics, and logging across their entire system from the start of development.

The project shows active development with regular commits across multiple areas of the codebase. Work spans core orchestration features, integrations with external services and platforms, and documentation improvements. The maintainers respond to issues and pull requests, indicating ongoing engagement with the community. Development activity demonstrates attention to both new capabilities and refinement of existing functionality based on user feedback.