T

GitHub Trending

t8y2/dbx

25 MB lightweight cross-platform database client for 100+ databases, including MySQL, PostgreSQL, SQLite, Redis, MongoDB, DuckDB, SQL Server, and Dameng. Built-in AI, MCP Server, CLI, desktop and Docker. | 轻量级跨平台数据库管理工具,支持 MySQL、PostgreSQL、SQLite、Redis、MongoDB、达梦等 100+ 数据库,提供桌面端、Docker、CLI、内置 AI 助手和 MCP。

RustsurgingLive GitHub sample
View JSON View on GitHub

Current momentum

89capped sample

Stars

27.1K

+450 since sync

Commits

100

in period

Active contributors

30

+0%

Issues closed

22

95.2h avg. resolution

Recorded trajectory

Movement you can verify over time.

Loading daily momentum history.

Behind the number

A score you can inspect.

Each signal contributes points to the total. These are capped GitHub samples, not complete activity counts or proof of adoption.

Development activity40.0 / 40 pts

100 commits · 53 opened PRs · 22 closed issues in 7 days

24 + 22 × ln(1 + weekly weighted activity). Activity = commits + 2 × opened PRs + closed issues. Signal bounded to 0–100, then weighted 40%.

Contributor breadth25.0 / 25 pts

30 sampled contributors in 7 days · 0% contributor-growth input

24 + 25 × ln(1 + contributors × √(7 / days)) + 0.15 × growth. Growth uses the 30-day windows; capped samples use a neutral 0 input. Signal bounded to 0–100, then weighted 25%.

Issue resolution9.1 / 20 pts

95.2 hours resolution input

105 − 9 × log₂(1 + hours). Uses sampled closed issues, not first-response time. With no resolved issues, the model uses 168 hours. Signal bounded to 0–100, then weighted 20%.

Release cadence15.0 / 15 pts

1 days cadence input

105 − 5 × cadence days. With fewer than two published releases, the model uses time since the last push as a proxy. Signal bounded to 0–100, then weighted 15%.

Weighted total · rounded once89 / 100

What changed in the recorded sample?

Loading recorded observations…

2.5K forks

Downstream adoption

1.2K open issues

Community demand

1 day cadence

Shipping consistency