Current repository readingScanned Jul 24, 2026, 8:03 PM UTC

kuma-ui Codebase Valuation

🐻‍❄️ A Headless, Utility-First, and Zero-Runtime UI Component Library ✨

View kuma-ui/kuma-ui on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/kuma-ui

kuma-ui

🐻‍❄️ A Headless, Utility-First, and Zero-Runtime UI Component Library ✨

RepoWorth$1,137Current measured development value · Less than one active build day
Rebuild complexity83.197/100Profile: Complex
82K code tokens217 source filesTypeScript primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/kuma-ui
Authored code82K tokens · 11,528 source lines
Complexity83.197/100 · Complex
Primary stackTypeScript
Scan coverage81.83% · 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
$1,137

Modeled range $852.72 to $1,535

0.7 active build days5.5 engineering hours69.4K implementation tokens
Repository evidenceMeasured at the scanned commit
82K tokens

11,528 source lines across 217 authored files

24 test files196 dependencies81.83% 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$1,137
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage82%current scan
Complexity83/100Measured from code scale and structural signals
Maintainability72/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
#1poteboy@poteboy20561.9%Current GitHub contributor snapshot
#2yukukotani@yukukotani298.8%Current GitHub contributor snapshot
#3kotarella1110@kotarella1110288.5%Current GitHub contributor snapshot
#4taishinaritomi@taishinaritomi247.3%Current GitHub contributor snapshot
#5thomaslindstrom@thomaslindstrom123.6%Current GitHub contributor snapshot
#6masa5555@masa5555123.6%Current GitHub contributor snapshot
#7nojiritakeshi@nojiritakeshi72.1%Current GitHub contributor snapshot
#8Karibash@Karibash51.5%Current GitHub contributor snapshot
#9naruaway@naruaway51.5%Current GitHub contributor snapshot
#10takurinton@takurinton41.2%Current GitHub contributor snapshot
About kuma-ui

What the public repository appears to contain.

🐻‍❄️ A Headless, Utility-First, and Zero-Runtime UI Component Library ✨

css-in-jsheadlessreactutility-firstzero-runtime
License
MIT
Default branch
main
GitHub stars
1,858
Forks
69
Last public push
May 29, 2026
Repository state
Active public repository
Detected language profile336.6KB authored source
TypeScript86.08%
JavaScript6.04%
Rust5.53%
CSS2.02%
HTML0.23%
Shell0.1%
Source files217
Test files24
Manifests18
Dependencies196
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 signal72/100

Established based on deterministic repository structure and complexity signals.

Production source67.2K tokens

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

Test evidence14.8K tokens

24 detected test files contribute separately from production code.

Configuration and infrastructure7.7K tokens

18 manifests and 0 workspace boundaries were detected.

Documentation54.8K tokens

55 documentation files remain visible as a distinct enablement signal.

Integration surface1,249 signals

196 dependency declarations and 316 public-interface signals were measured.

Repository structure6 levels deep

0 large files and 887 branch signals add structural context.

Excluded from authored evidence0 files

2 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

Integration surface

At least 1,000 deterministic integration signals were measured in source.

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 scaleModerate

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 evidence69.4KProduction, tests, configuration, and documentation
Estimated implementation output69.4KImplementation, retries, integration, and verification
Engineering oversight5.5 hoursOrientation, integration, tests, and review
Active build time0.7 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

CodeValuation.com counted supported authored source on commit 05cbbb0b880c71be99b9aaa233a1e6531d6466ac, 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.