davidfowl/TodoApp

Todo application with ASP.NET Core Blazor WASM, Minimal APIs and Authentication

View on GitHub ↗Jump to charts ↓

davidfowl/TodoApp has 3k+ stars and 450+ forks on GitHub, is written in C#, and was last pushed on Feb 12, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on May 4th, 2021
Open Issues & Pull Requests: 5 (+0)
GitHub issues: Enabled
Number of forks: 468
Total Stargazers: 3,100 (+0)
Total Subscribers: 72 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 23.8 days
Mean response time: 178.9 days
90th percentile: 739.0 days
Tracked items: 8

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

TodoApp is a sample full-stack web application built with ASP.NET Core that demonstrates Blazor WebAssembly for the frontend and Minimal APIs for the backend.

The application addresses the need to learn how modern ASP.NET Core patterns work together in a realistic scenario. It combines a Blazor WASM frontend with a REST API backend, using Entity Framework and SQLite for data persistence. The frontend runs as a hosted Blazor application that proxies requests to the backend API using YARP's IHttpForwarder. Authentication is handled through both cookie-based and bearer token approaches, with support for user registration and login flows.

This project suits developers learning ASP.NET Core architecture or those building similar full-stack applications. It demonstrates integration of multiple authentication strategies including username and password, social providers like GitHub and Google, and OIDC through Auth0. The codebase includes rate limiting, OpenAPI documentation, and integration tests for the REST API. The project runs via the Aspire AppHost, which orchestrates both the web and API components along with their dependencies.

The project shows consistent maintenance with regular updates to align with current .NET versions and platform features. Development activity reflects active engagement with modern ASP.NET Core tooling, including adoption of Aspire for application orchestration and OpenTelemetry for observability. The codebase demonstrates attention to security practices, particularly around credential management and authentication configuration.