dapperlib/dapper

Dapper - a simple object mapper for .Net

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 7 minutes ago
Added to GitGenius on September 3rd, 2026
Created on April 14th, 2011
Open Issues & Pull Requests: 547 (+0)
GitHub issues: Enabled
Number of forks: 3,669
Total Stargazers: 18,380 (+0)
Total Subscribers: 920 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.7 hours
Mean response time: 77.3 days
90th percentile: 200.9 days
Tracked items: 119

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Only 2% of issues opened in the past year have been closed. Three people close 57% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 93
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,458 days
Stale 30+ days: 83
Stale 90+ days: 73

Recent activity

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

Top labels

  • bug (23)
  • needs-triage (19)
  • enhancement (5)
  • v3.0 (3)
  • feature request (2)
  • needs-info (2)
  • needs-investigation (2)
  • proposal (2)

Detailed Description

Dapper is a lightweight object mapper for .NET that maps the results of SQL queries directly onto plain objects with minimal overhead.

The tool solves the problem of bridging the gap between raw ADO.NET query results and strongly-typed objects without the complexity of a full ORM. It works by extending IDbConnection with methods that execute SQL commands and automatically map the returned data rows to object properties, allowing developers to write direct SQL while still gaining type safety and reduced boilerplate compared to manual result processing.

Dapper suits projects where developers prefer control over their SQL queries and want to avoid the performance penalties and learning curve of heavyweight ORMs. It works well in scenarios ranging from simple CRUD operations to complex queries where SQL optimization matters. The tool is particularly valuable in performance-sensitive applications and microservices where a minimal dependency footprint is important. Teams should choose Dapper if they are comfortable writing SQL directly and want an efficient bridge to objects rather than an abstraction layer that generates queries.

The project maintains a substantial base of real-world adopters, as evidenced by the fact that almost all open issues are raised by outside users rather than the core team. Maintainers typically respond to new issues and pull requests within a day.