Current repository readingScanned Jul 19, 2026, 5:46 PM UTC

nanobot Codebase Valuation

Lightweight, open-source AI agent for your tools, chats, and workflows.

View HKUDS/nanobot on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/HKUDS

nanobot

Lightweight, open-source AI agent for your tools, chats, and workflows.

RepoWorth$24,405Current measured development value · 17.4 active build days
Rebuild complexity93.275/100Profile: Complex
2.1M code tokens756 source filesPython primary language
Scanned Jul 19, 2026Public GitHub repositorycodevaluation.com/repoworth/nanobot
Authored code2.1M tokens · 258,654 source lines
Complexity93.275/100 · Complex
Primary stackPython
Scan coverage99.87% · 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
$24,405

Modeled range $19,524 to $29,286

17.4 active build days112.8 engineering hours1.7M implementation tokens
Repository evidenceMeasured at the scanned commit
2.1M tokens

258,654 source lines across 756 authored files

349 test files200 dependencies99.87% 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$24,405
Current measured reading
Measured · Jul 19, 2026Data through · Jul 19, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity93/100Measured from code scale and structural signals
Maintainability69/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.

RankContributorContributionsShare of top groupLatest measured activity
#1Xubin Ren@Re-bin1,58261.8%Current GitHub contributor snapshot
#2chengyongru@chengyongru68126.6%Current GitHub contributor snapshot
#3Stellar鱼@yu-xin-c692.7%Current GitHub contributor snapshot
#4Alexander Minges@Athemis471.8%Current GitHub contributor snapshot
#5axelray-dev@axelray-dev421.6%Current GitHub contributor snapshot
#6yorkhellen@yorkhellen361.4%Current GitHub contributor snapshot
#704cb@04cb341.3%Current GitHub contributor snapshot
#8Kunal Karmakar@kunalk16240.9%Current GitHub contributor snapshot
#9San_Check@xcosmosbox240.9%Current GitHub contributor snapshot
#10chaohuang-ai@chaohuang-ai210.8%Current GitHub contributor snapshot
About nanobot

What the public repository appears to contain.

Lightweight, open-source AI agent for your tools, chats, and workflows.

aiai-agentai-agentsanthropicchatgptclaudeclaude-codecodexcodex-clillmnanobotopenai
License
MIT
Default branch
main
GitHub stars
45,887
Forks
8,109
Last public push
Jul 19, 2026
Repository state
Active public repository
Detected language profile9.1MB authored source
Python76.81%
TypeScript22.64%
Shell0.24%
CSS0.19%
HTML0.07%
JavaScript0.05%
Source files756
Test files349
Manifests2
Dependencies200
Measured technical evidence

A fuller view of what the scanner found.

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 signal69/100

Established based on deterministic repository structure and complexity signals.

Production source1M tokens

First-party implementation tokens eligible for the modeled code-scale input.

Test evidence1.1M tokens

349 detected test files contribute separately from production code.

Configuration and infrastructure2K tokens

2 manifests and 0 workspace boundaries were detected.

Documentation149.6K tokens

95 documentation files remain visible as a distinct enablement signal.

Integration surface7,438 signals

200 dependency declarations and 491 public-interface signals were measured.

Repository structure5 levels deep

0 large files and 23,741 branch signals add structural context.

Excluded from authored evidence0 files

0 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.

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.

quality

Verification depth

At least 20 percent of measured source tokens are in test paths.

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 evidence1.7MProduction, tests, configuration, and documentation
Estimated implementation output1.7MImplementation, retries, integration, and verification
Engineering oversight112.8 hoursOrientation, integration, tests, and review
Active build time17.4 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

CodeValuation.com counted supported authored source on commit e3de01c9f61d026fa7c9638810f8878f100c2927, measured deterministic repository signals, then estimated implementation, rework, testing, integration, and engineering oversight.

Included

Supported first-party source, tests, configuration, manifests, repository structure, dependency signals, and framework boundaries.

Excluded

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.

No sign-up for public repositories. Private repositories require a free trial. Evaluated in real time directly from GitHub. Code is never stored. Derived measurements and valuation history are saved.