sqlitebrowser

sqlitebrowser/sqlitebrowser

Official home of the DB Browser for SQLite (DB4S) project. Previously known as "SQLite Database Browser" and "Database Browser for SQLite". Website at:

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 16, 2026
today
Ship score
93/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 24,544 → 24,694 (Sep 1 – Oct 13, 2026)
+98 stars in the 28 days to 2026-10-13

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
24.7K
Forks
2.4K
Open issues
834
Watchers
502
Primary language
C++
License
Other
Created
May 4, 2014
Owner
sqlitebrowser · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. License unknown — GitHub’s own license field, not legal advice. 31 startups in the directory ship primarily in C++.

Topics

#c-plus-plus#cross-platform#database#database-browser#database-gui#sqlite#sqlitebrowser

How it got here

What the classifier decided, and when.

Read by Jev, TypeSafe’s classifier, on Sep 22, 2026, which did not call this an open-source startup — it chose something else instead, and put os_startup at 14% (self-hostable 46%, hosted offering 8%). The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory. This one is in that queue, waiting for a person — removing a listing is a pull request a human opens.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-16This is the badge for sqlitebrowser/sqlitebrowser, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/sqlitebrowser/sqlitebrowser.svg)](https://ossean.com/sqlitebrowser/sqlitebrowser)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.