20 MB lightweight cross-platform database client for 70+ 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、达梦等 70+ 数据库，提供桌面端、Docker、CLI、内置 AI 助手和 MCP Server。
RepoWorth$83,792Current measured development value · 46.9 active build days
Rebuild complexity100/100Profile: Complex
5.9M code tokens2K source filesRust primary language
Authored code5.9M tokens · 608,554 source lines
Complexity100/100 · Complex
Primary stackRust
Scan coverage100% · Content scan
RepoWorth development valuation
One valuation, with the evidence behind it.
RepoWorth models the current development value represented by the visible repository evidence. It does not include ideation, intellectual property, business value, product discovery, or sale price.
RepoWorthCurrent measured development value$83,792
Modeled range $67,034 to $100,551
46.9 active build days375.4 engineering hours4.7M implementation tokens
Repository evidenceMeasured at the scanned commit5.9M tokens
608,554 source lines across 1,973 authored files
656 test files998 dependencies100% scan coverage
Repository evidence
Building the historical and contribution view.
The headline RepoWorth and measured source facts are ready. Comparable history, accepted changes, and badge evidence will appear here as enrichment finishes.
Repository contributors
Top contributors.
Ranked from the public GitHub contributor evidence available at the latest scan. This table describes measured repository activity, not ownership or original authorship.
These values come from the same immutable repository scan as the headline RepoWorth. They stay tied to the scanned commit so the reading can be inspected against one exact source state.
Maintainability signal62/100
Established based on deterministic repository structure and complexity signals.
Production source4.9M tokens
First-party implementation tokens eligible for the modeled code-scale input.
Test evidence1M tokens
656 detected test files contribute separately from production code.
Configuration and infrastructure8.1K tokens
72 manifests and 0 workspace boundaries were detected.
Documentation169.7K tokens
129 documentation files remain visible as a distinct enablement signal.
Integration surface27,006 signals
998 dependency declarations and 5,998 public-interface signals were measured.
Repository structure11 levels deep
0 large files and 92,946 branch signals add structural context.
Excluded from authored evidence0 files
4 generated files were identified. Ignored and generated material does not inflate RepoWorth.
Measured repository distinctions
Repository evidence highlights.
Each highlight records a measured characteristic of the same repository scan used for this RepoWorth report.
architecture
Interface builder
At least 500 deterministic public interface signals were measured in source.
architecture
Integration mesh
At least 10,000 deterministic integration signals were measured in source.
enablement
Documented foundation
At least 100,000 documentation tokens were measured in public documentation paths.
architecture
Integration surface
At least 1,000 deterministic integration signals were measured in source.
breadth
Polyglot system
At least five languages each represent one percent or more of measured source tokens.
architecture
Dependency ecosystem
At least 500 dependency declarations were measured across supported manifests.
Technical effort profile
What makes this repository harder to rebuild.
Code scale, branching, dependencies, languages, structure, and visible test evidence shape the implementation and verification effort represented by this repository.
Code scaleHigh
Measured from the current source archive.
ComplexityHigh
Derived from branch density, dependencies, languages, and code scale.
VerificationHigh
Measures visible test code relative to the source corpus.
Development effort composition
Source volume alone does not explain the work.
This view separates authored evidence from the implementation, integration, verification, and engineering oversight represented by the current repository.
Reading boundary: These are modeled development inputs for the visible code. They do not include product discovery, company value, private systems, or commercial outcomes.
Weighted authored evidence4.7MProduction, tests, configuration, and documentation
Estimated implementation output4.7MImplementation, retries, integration, and verification
Engineering oversight375.4 hoursOrientation, integration, tests, and review
Active build time46.9 daysModeled effort represented by the current source state
Evidence boundary
What this valuation includes.
CodeValuation.com counted supported authored source on commit e6da0a6298a1507591b6580a6aed26511d8f0768, measured deterministic repository signals, then estimated implementation, rework, testing, integration, and engineering oversight.
Common generated and vendored files, build output, dependencies, lockfiles, minified assets, binaries, media, and private systems outside this repository.
Not claimed
Ideation, intellectual-property rights, security posture, production reliability, company value, sale price, revenue, user value, proprietary data, or the cost of discovering the original product.
This is a modeled current development valuation for the repository's visible code at a specific commit. It reflects code volume, implementation output, complexity, and engineering oversight. It is not a business valuation, investment appraisal, security review, or estimate of sale price, ideation, intellectual property, revenue, users, brand, proprietary data, undocumented domain knowledge, or private infrastructure.
Check another repository
Run RepoWorth on your own codebase.
Enter a public GitHub URL to create a current repository reading.
