microsoft/aspire
Aspire is the tool for code-first, extensible, observable dev and deploy.
Is microsoft/aspire beginner-friendly?
In the last 30 days, microsoft/aspire merged 44 of 87 pull requests from outside contributors, and its maintainers usually reply within 2 days. 70 beginner-friendly issues are open now.
- Stars
- 6.4k
- Forks
- 1k
- Open beginner issues
- 70
- Indexed issues
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 349
- Dominant language
- C#
- License
- MIT
- Last GitHub push
- Nov 2, 2026
- Latest indexed
- Sep 17, 2026
- Contributing guide
- Contributing guide
- Code of conduct
- Code of conduct
- Beginner labels
- good first issue help wanted
How to contribute to microsoft/aspire
- Read the contributing guide first: it says how the maintainers want changes proposed, tested and reviewed.
- The project ships a dev container: open it in Codespaces to get a working environment in your browser.
- Read its code of conduct: it covers issues and pull requests as well as chat.
- Pick one of the 70 open beginner-friendly issues below and comment that you want to work on it before you start.
Issues somebody may already be working on are listed last. List everything by date
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 2 days
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 2 days
-
agentic-workflows needs-area-label
Difficulty 3/5 Half a day Newbie friendliness 25/100
Maintainers usually reply within 2 days
-
agentic-workflows area-integrations
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 2 days
-
agentic-workflows
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
Maintainers usually reply within 2 days
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Maintainers usually reply within 2 days
-
agentic-workflows
Difficulty 4/5 1-2 days Newbie friendliness 20/100
Maintainers usually reply within 2 days
-
needs-area-label
Difficulty 3/5 1-2 days Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
area-dashboard dashboard-persistence enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 2 days
-
area-dashboard bug dashboard-persistence
Difficulty 5/5 Over a week Newbie friendliness 20/100
microsoft/aspire#21901 · 2 comments ·
Maintainers usually reply within 2 days
-
area-integrations
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 2 days
-
area-app-model
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 2 days
-
needs-area-label
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 2 days
-
area-deployment
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Maintainers usually reply within 2 days
-
area-integrations
Difficulty 5/5 Over a week Newbie friendliness 20/100
Maintainers usually reply within 2 days
-
Dashboard structured logs toolbar overlaps the resource name and wraps poorly in constrained layoutsOpenarea-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 2 days
-
area-tooling
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/aspire#21865 · 1 comment ·
Maintainers usually reply within 2 days
-
area-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
area-dashboard
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 2 days
-
area-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
area-templates
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 2 days
-
area-templates
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 2 days
-
area-templates
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 2 days
-
ci-failure-cause test-failure
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 2 days
-
needs-area-label
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 2 days
-
area-integrations
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 2 days
-
ATS provisioning exports lose base-receiver methods when inherited capabilities target derived typesOpenneeds-area-label
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Maintainers usually reply within 2 days
-
ci-failure-cause test-failure
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 2 days
-
ci-failure-cause test-failure
Difficulty 3/5 1-2 days Newbie friendliness 58/100
Maintainers usually reply within 2 days
-
needs-area-label
Difficulty 1/5 Under an hour Newbie friendliness 1/100
Maintainers usually reply within 2 days
-
needs-area-label
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 2 days
-
area-engineering-systems ci-failure-cause
Difficulty 1/5 Under an hour Newbie friendliness 1/100
Maintainers usually reply within 2 days
-
ci-failure-cause ci-test-failure test-failure
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Maintainers usually reply within 2 days
-
breaking-change bug needs-area-label
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 2 days
-
ci-failure-cause ci-test-failure test-failure
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 2 days
-
area-app-model
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 2 days
-
area-extension
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 2 days
-
[CI Failure] Flaky: SqlServerReplCommandTests fail because sqlserver container never becomes healthyOpenci-failure-cause ci-test-failure test-failure
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Maintainers usually reply within 2 days
-
ci-failure-cause ci-test-failure test-failure
Difficulty 3/5 1-2 days Newbie friendliness 57/100
Maintainers usually reply within 2 days
-
area-integrations azure
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 2 days
-
ci-failure-cause ci-test-failure test-failure
Difficulty 3/5 1-2 days Newbie friendliness 64/100
Maintainers usually reply within 2 days
-
area-cli
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Maintainers usually reply within 2 days
-
area-cli
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 2 days
-
needs-area-label
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
needs-area-label
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 2 days
-
area-integrations
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 2 days
-
ci-failure-cause ci-workflow-health main-ci-break
Difficulty 3/5 1-2 days Newbie friendliness 43/100
Maintainers usually reply within 2 days
-
needs-area-label
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 2 days
-
Generated TypeScript integration project fails in SHA-256 worktrees and hides the SourceLink errorOpenarea-integrations
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 2 days
-
area-integrations
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 2 days
Showing the newest 100
This page lists what was indexed most recently. Advanced filter has the whole inventory, narrowed by language, difficulty and how long a task takes.