davidfowl/Todos
Various todo list backend API implementations observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases no_license
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 2398
- days_rel: n/a
- days_push: 1390
- n_releases_24m: 0
Adoption not part of the score
1036 stars · 145 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
A collection of todo list backend API implementations written in C# for .NET Core. It serves as reference sample code demonstrating different ways to build the same backend API.
Use cases
- compare different ways to build a todo backend API in .NET Core
- learn ASP.NET Core minimal API patterns from working examples
- use as a starting point for building a CRUD backend in C#
- study reference implementations of a simple REST API
- evaluate .NET Core backend approaches side by side
When to choose
- you want sample .NET Core backend code to learn from or copy
- you need a minimal working API example in C# to bootstrap a project
- you want to compare multiple implementation styles of the same API
When to avoid
- you need a production-ready todo application with a frontend and persistence guarantees
- you require a licensed, maintained product with releases and support
- you are not working in the .NET/C# ecosystem
Facets
application · maturity experimental
http-server api-framework developer-tools web-development backend apis developer-tools dotnet cross-platform todo-app sample-code aspnet-core minimal-apis reference-implementation csharp backend-api learning-examples web-server
1 source
- readme: https://github.com/davidfowl/Todos · fetched 2026-08-28 · d2f7f3efa568
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| davidfowl/Todos | main | 32 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem