Current repository readingScanned Jul 24, 2026, 12:59 PM UTC

Kaku Codebase Valuation

๐ŸŽƒ A fast, out-of-the-box terminal built for AI coding.

View tw93/Kaku on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/tw93

Kaku

๐ŸŽƒ A fast, out-of-the-box terminal built for AI coding.

RepoWorth$50,920Current measured development value ยท 28.6 active build days
Rebuild complexity99.733/100Profile: Complex
3.4M code tokens802 source filesRust primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/kaku
Authored code3.4M tokens ยท 454,337 source lines
Complexity99.733/100 ยท Complex
Primary stackRust
Scan coverage85.14% ยท 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
$50,920

Modeled range $38,190 to $68,742

28.6 active build days228.4 engineering hours2.9M implementation tokens
Repository evidenceMeasured at the scanned commit
3.4M tokens

454,337 source lines across 802 authored files

30 test files1,883 dependencies85.14% 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$50,920
Current measured reading
Measured ยท Jul 24, 2026Data through ยท Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage85%current scan
Complexity100/100Measured from code scale and structural signals
Maintainability38/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
#1tw93@tw931,27095.6%Current GitHub contributor snapshot
#2darion-yaphet@darion-yaphet120.9%Current GitHub contributor snapshot
#3GavinRiver@GavinRiver90.7%Current GitHub contributor snapshot
#4WongLoki@WongLoki70.5%Current GitHub contributor snapshot
#5claude@claude70.5%Current GitHub contributor snapshot
#6mortalYoung@mortalYoung60.5%Current GitHub contributor snapshot
#7nguyenphutrong@nguyenphutrong60.5%Current GitHub contributor snapshot
#8t0m-car@t0m-car50.4%Current GitHub contributor snapshot
#9liu-kan@liu-kan40.3%Current GitHub contributor snapshot
#10Frank Yang@frankekn30.2%Current GitHub contributor snapshot
About Kaku

What the public repository appears to contain.

๐ŸŽƒ A fast, out-of-the-box terminal built for AI coding.

ai-codingmacosrustserialterminalterminal-appterminal-emulatorvibe-coding
License
NOASSERTION
Default branch
main
GitHub stars
5,666
Forks
284
Last public push
Jul 19, 2026
Repository state
Active public repository
Detected language profile14.9MB authored source
Rust54.24%
C35.65%
C/C++6.84%
Shell2.21%
Lua1.05%
Python0.01%
Source files802
Test files30
Manifests69
Dependencies1,883
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 signal38/100

Developing based on deterministic repository structure and complexity signals.

Production source3.4M tokens

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

Test evidence50.9K tokens

30 detected test files contribute separately from production code.

Configuration and infrastructure15.4K tokens

69 manifests and 0 workspace boundaries were detected.

Documentation4.9M tokens

70 documentation files remain visible as a distinct enablement signal.

Integration surface298 signals

1,883 dependency declarations and 3 public-interface signals were measured.

Repository structure5 levels deep

0 large files and 49,698 branch signals add structural context.

Excluded from authored evidence0 files

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

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.

enablement

Documentation atlas

More than one million measured documentation tokens support the public codebase.

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 evidence2.9MProduction, tests, configuration, and documentation
Estimated implementation output2.9MImplementation, retries, integration, and verification
Engineering oversight228.4 hoursOrientation, integration, tests, and review
Active build time28.6 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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