praeclarum/sqlite-net

Simple, powerful, cross-platform SQLite client and ORM for .NET

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 32 minutes ago
Added to GitGenius on September 15th, 2026
Created on April 26th, 2011
Open Issues & Pull Requests: 615 (+0)
GitHub issues: Enabled
Number of forks: 1,420
Total Stargazers: 4,458 (+0)
Total Subscribers: 198 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.9 days
Mean response time: 331.4 days
90th percentile: 1485.6 days
Tracked items: 70

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 79
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,454 days
Stale 30+ days: 76
Stale 90+ days: 72

Recent activity

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

Top labels

  • Feature (3)
  • Bug (2)
  • Question (2)
  • Up for Grabs (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

sqlite-net is a lightweight ORM and SQLite client for .NET that enables cross-platform database access across .NET, .NET Core, Mono, Xamarin, UWP, and Azure environments.

The tool addresses the need for straightforward SQLite integration in .NET applications without requiring developers to restructure their data models. It works as a thin wrapper over SQLite, providing reflection-driven ORM capabilities that map existing classes directly to database tables. CRUD operations and queries execute safely through parameterized statements, with results returned in strongly typed form. The library is distributed in multiple NuGet packages to accommodate different deployment scenarios: a .NET Standard version for broad compatibility, a static version using P/Invoke to platform-provided SQLite, and a base version allowing custom SQLitePCLRaw providers.

Developers should choose this tool when they need minimal friction in adding SQLite persistence to existing .NET projects without performance overhead or architectural constraints. It suits applications where a lightweight database layer is preferable to heavier ORMs, and where the ability to add the library as a single source file offers deployment flexibility. The README positions it as designed for quick integration and convenience rather than as a feature-rich alternative to larger frameworks.

The project maintains active continuous integration through GitHub Actions with code coverage reporting. Development activity shows responsiveness to community contributions, with the maintainers explicitly welcoming issues, suggestions, and pull requests through documented contribution guidelines.