Current repository readingScanned Jul 24, 2026, 3:04 PM UTC
MuseBot Codebase Valuation
supports Telegram, Discord, Slack, Lark（飞书），钉钉, 企业微信, QQ, 微信, compatible with various LLMs including OpenAI, Gemini, DeepSeek, Doubao, and OpenRouter. It offers intelligent conversation, image generation, video creation, and more. Works seamlessly in both private chats and group settings.
supports Telegram, Discord, Slack, Lark（飞书），钉钉, 企业微信, QQ, 微信, compatible with various LLMs including OpenAI, Gemini, DeepSeek, Doubao, and OpenRouter. It offers intelligent conversation, image generation, video creation, and more. Works seamlessly in both private chats and group settings.
RepoWorth$6,353Current measured development value · 3.7 active build days
Rebuild complexity90.476/100Profile: Complex
505.5K code tokens139 source filesGo primary language
Authored code505.5K tokens · 32,005 source lines
Complexity90.476/100 · Complex
Primary stackGo
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$6,353
Modeled range $5,082 to $7,624
3.7 active build days29.9 engineering hours373.4K implementation tokens
Repository evidenceMeasured at the scanned commit505.5K tokens
32,005 source lines across 139 authored files
22 test files231 dependencies100% scan coverage
Measured RepoWorth history
The current RepoWorth starts the measured history.
This current scan is the first measured point. Later scans add comparable history when the repository changes. RepoWorth is not back-cast onto commits that were never scanned.
Recorded RepoWorth$6,353
Current measured reading
Measurement basisCurrent readingCurrent published repository scanEvidence coverage100%current scanComplexity90/100Measured from code scale and structural signalsMaintainability58/100Current structure, tests, and generated-code balance
This current scan establishes the RepoWorth baseline. Comparable value changes appear only after another completed scan under the same measurement basis.
RepoWorth history compares completed repository scans only when their measurement basis is compatible. Commit activity is shown separately so delivery volume is not presented as code value.
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.
supports Telegram, Discord, Slack, Lark（飞书），钉钉, 企业微信, QQ, 微信, compatible with various LLMs including OpenAI, Gemini, DeepSeek, Doubao, and OpenRouter. It offers intelligent conversation, image generation, video creation, and more. Works seamlessly in both private chats and group settings.
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 signal58/100
Developing based on deterministic repository structure and complexity signals.
Production source466.8K tokens
First-party implementation tokens eligible for the modeled code-scale input.
Test evidence38.6K tokens
22 detected test files contribute separately from production code.
Configuration and infrastructure718 tokens
2 manifests and 0 workspace boundaries were detected.
Documentation68.6K tokens
60 documentation files remain visible as a distinct enablement signal.
Integration surface489 signals
231 dependency declarations and 15 public-interface signals were measured.
Repository structure5 levels deep
0 large files and 14,054 branch signals add structural context.
Excluded from authored evidence0 files
3 generated files were identified. Ignored and generated material does not inflate RepoWorth.
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.
VerificationLow
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 evidence373.4KProduction, tests, configuration, and documentation
Estimated implementation output373.4KImplementation, retries, integration, and verification
Engineering oversight29.9 hoursOrientation, integration, tests, and review
Active build time3.7 daysModeled effort represented by the current source state
Evidence boundary
What this valuation includes.
CodeValuation.com counted supported authored source on commit 28d5c9ce38e279fb51124cf334ab28d7c30e15ec, 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.
