Database client dbx has 1,256 open issues, 58 open PRs

dbx is a 20 MB cross-platform database client that connects to more than 90 engines, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, and DuckDB. It's picked up 18,630 stars and grew by 336 in a day. It also has 1,256 open issues against just 58 open pull requests.

That's a 21:1 ratio. GitHub's repo page shows a single open_issues_count number that folds issues and PRs together, so the gap doesn't show up unless someone pulls the two counts apart and compares them. Once you do, the story is a tool with real reach and a maintainer team fielding bug reports mostly by themselves.

For comparison, vercel-labs/agent-browser sits at 356 PRs against 348 issues, checked the same hour. That's close to even, the shape you'd expect from a project where users who hit a bug are also the ones capable of patching it. dbx's ratio says something different: a lot of people are running it against production databases and filing what breaks, but few are sending the fix themselves. That tracks with what the project is. Wiring up 90 different engines under one client takes domain knowledge most users filing a Redis timeout bug won't have.

A repo carrying that many open issues against a small core team is a maintenance bet. If issue volume keeps outpacing PR volume, the backlog only grows, and the people best positioned to judge whether that's a problem are the ones already running dbx against something that matters. Watch whether the PR count moves at all over the next few weeks, or whether it's the issue count doing all the growing.