Current repository readingScanned Jul 24, 2026, 11:04 PM UTC

instrument Codebase Valuation

A calm, powerful, private AI workspace, perfectly at home on your computer.

View instrument-org/instrument on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/instrument-org

instrument

A calm, powerful, private AI workspace, perfectly at home on your computer.

RepoWorth$15,264Current measured development value · 8.8 active build days
Rebuild complexity94.704/100Profile: Complex
1.1M code tokens1.1K source filesTypeScript primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/instrument
Authored code1.1M tokens · 130,424 source lines
Complexity94.704/100 · Complex
Primary stackTypeScript
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
$15,264

Modeled range $12,211 to $18,317

8.8 active build days70.2 engineering hours877.8K implementation tokens
Repository evidenceMeasured at the scanned commit
1.1M tokens

130,424 source lines across 1,094 authored files

145 test files300 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$15,264
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity95/100Measured from code scale and structural signals
Maintainability66/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.

52-week repository activity

3,845 commits across the public default-branch history.

Commit activity provides delivery context. It does not assign a historical RepoWorth to unscanned commits or treat commit count as value.

Jul 27, 2025Weekly commitsJul 19, 2026

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
#1mutewinter@mutewinter3,63294.4%Current GitHub contributor snapshot
#2aortbals@aortbals1734.5%Current GitHub contributor snapshot
#3neilrenicker@neilrenicker381.0%Current GitHub contributor snapshot
#4claude@claude20.1%Current GitHub contributor snapshot
#5spinualexandru@spinualexandru20.1%Current GitHub contributor snapshot
#6cursoragent@cursoragent20.1%Current GitHub contributor snapshot
About instrument

What the public repository appears to contain.

A calm, powerful, private AI workspace, perfectly at home on your computer.

License
Apache-2.0
Default branch
main
GitHub stars
1
Forks
0
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile4.3MB authored source
TypeScript89.77%
JavaScript9.29%
CSS0.64%
Shell0.23%
HTML0.07%
Source files1,094
Test files145
Manifests9
Dependencies300
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 signal66/100

Established based on deterministic repository structure and complexity signals.

Production source877.9K tokens

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

Test evidence191.6K tokens

145 detected test files contribute separately from production code.

Configuration and infrastructure9K tokens

9 manifests and 0 workspace boundaries were detected.

Documentation70.5K tokens

77 documentation files remain visible as a distinct enablement signal.

Integration surface12,375 signals

300 dependency declarations and 1,745 public-interface signals were measured.

Repository structure9 levels deep

0 large files and 14,869 branch signals add structural context.

Excluded from authored evidence0 files

3 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

Interface builder

At least 500 deterministic public interface signals were measured in source.

architecture

Integration mesh

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

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 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 evidence877.8KProduction, tests, configuration, and documentation
Estimated implementation output877.8KImplementation, retries, integration, and verification
Engineering oversight70.2 hoursOrientation, integration, tests, and review
Active build time8.8 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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