Current repository readingScanned Jul 25, 2026, 12:00 AM UTC

maki Codebase Valuation

An efficient AI coding agent extendable by neovim like Lua plugins

View tontinton/maki on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/tontinton

maki

An efficient AI coding agent extendable by neovim like Lua plugins

RepoWorth$17,271Current measured development value · 9.8 active build days
Rebuild complexity96.54/100Profile: Complex
1.2M code tokens362 source filesRust primary language
Scanned Jul 25, 2026Public GitHub repositorycodevaluation.com/repoworth/maki
Authored code1.2M tokens · 148,281 source lines
Complexity96.54/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
$17,271

Modeled range $13,817 to $20,725

9.8 active build days78.7 engineering hours984K implementation tokens
Repository evidenceMeasured at the scanned commit
1.2M tokens

148,281 source lines across 362 authored files

49 test files510 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$17,271
Current measured reading
Measured · Jul 25, 2026Data through · Jul 25, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity97/100Measured from code scale and structural signals
Maintainability56/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
#1tontinton@tontinton1,39190.3%Current GitHub contributor snapshot
#2sdroege@sdroege432.8%Current GitHub contributor snapshot
#3g4bwy@g4bwy221.4%Current GitHub contributor snapshot
#4smores56@smores56201.3%Current GitHub contributor snapshot
#5lu-zero@lu-zero181.2%Current GitHub contributor snapshot
#6jjmaestro@jjmaestro151.0%Current GitHub contributor snapshot
#7w0wl0lxd@w0wl0lxd100.6%Current GitHub contributor snapshot
#8cybershape@cybershape100.6%Current GitHub contributor snapshot
#9TheTiresias@TheTiresias60.4%Current GitHub contributor snapshot
#10elasticdog@elasticdog50.3%Current GitHub contributor snapshot
About maki

What the public repository appears to contain.

An efficient AI coding agent extendable by neovim like Lua plugins

License
MIT
Default branch
main
GitHub stars
756
Forks
85
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile4.8MB authored source
Rust80.56%
Lua14.36%
HTML2.73%
CSS1.13%
Python1.05%
Shell0.16%
Source files362
Test files49
Manifests14
Dependencies510
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 signal56/100

Developing based on deterministic repository structure and complexity signals.

Production source1.1M tokens

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

Test evidence114.6K tokens

49 detected test files contribute separately from production code.

Configuration and infrastructure4.1K tokens

14 manifests and 0 workspace boundaries were detected.

Documentation56K tokens

24 documentation files remain visible as a distinct enablement signal.

Integration surface275 signals

510 dependency declarations and 44 public-interface signals were measured.

Repository structure4 levels deep

0 large files and 12,212 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.

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.

VerificationModerate

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 evidence984KProduction, tests, configuration, and documentation
Estimated implementation output984KImplementation, retries, integration, and verification
Engineering oversight78.7 hoursOrientation, integration, tests, and review
Active build time9.8 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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