Current repository readingScanned Jul 24, 2026, 10:02 PM UTC

aspire Codebase Valuation

Aspire is the tool for code-first, extensible, observable dev and deploy.

View microsoft/aspire on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/microsoft

aspire

Aspire is the tool for code-first, extensible, observable dev and deploy.

RepoWorth$160,066Current measured development value · 89.6 active build days
Rebuild complexity100/100Profile: Complex
11.2M code tokens5.1K source filesC# primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/aspire
Authored code11.2M tokens · 1,189,325 source lines
Complexity100/100 · Complex
Primary stackC#
Scan coverage92.02% · 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
$160,066

Modeled range $128,052 to $192,079

89.6 active build days717.0 engineering hours9M implementation tokens
Repository evidenceMeasured at the scanned commit
11.2M tokens

1,189,325 source lines across 5,095 authored files

1,855 test files1,170 dependencies92.02% 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$160,066
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage92%current scan
Complexity100/100Measured from code scale and structural signals
Maintainability62/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
#1JamesNK@JamesNK1,02322.5%Current GitHub contributor snapshot
#2eerhardt@eerhardt54412.0%Current GitHub contributor snapshot
#3mitchdenny@mitchdenny53811.8%Current GitHub contributor snapshot
#4davidfowl@davidfowl53011.6%Current GitHub contributor snapshot
#5joperezr@joperezr4119.0%Current GitHub contributor snapshot
#6sebastienros@sebastienros4038.9%Current GitHub contributor snapshot
#7adamint@adamint3928.6%Current GitHub contributor snapshot
#8radical@radical3597.9%Current GitHub contributor snapshot
#9danegsta@danegsta1864.1%Current GitHub contributor snapshot
#10DamianEdwards@DamianEdwards1653.6%Current GitHub contributor snapshot
About aspire

What the public repository appears to contain.

Aspire is the tool for code-first, extensible, observable dev and deploy.

clouddotnethacktoberfestpythontypescript
License
MIT
Default branch
main
GitHub stars
6,186
Forks
937
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile51.7MB authored source
C#73.6%
TypeScript12.14%
Go3.32%
Java3.23%
Rust2.99%
Python1.94%
JavaScript1.17%
Shell1.09%
Source files5,095
Test files1,855
Manifests167
Dependencies1,170
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 signal62/100

Established based on deterministic repository structure and complexity signals.

Production source4.6M tokens

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

Test evidence6.6M tokens

1,855 detected test files contribute separately from production code.

Configuration and infrastructure28.8K tokens

167 manifests and 0 workspace boundaries were detected.

Documentation834.9K tokens

489 documentation files remain visible as a distinct enablement signal.

Integration surface10,991 signals

1,170 dependency declarations and 27,918 public-interface signals were measured.

Repository structure10 levels deep

0 large files and 126,193 branch signals add structural context.

Excluded from authored evidence0 files

308 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

Interface city

At least 10,000 deterministic public-interface signals were measured in source.

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.

scale

System-scale codebase

More than 10 million measured source tokens in one qualifying snapshot.

quality

Verification depth

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

complexity

Branching engine

At least 100,000 deterministic control-flow and branch signals were measured in source.

operations

Infrastructure backbone

At least 100,000 measured tokens are in explicit infrastructure and deployment 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.

quality

Test fortress

At least 35 percent of measured source tokens are in detected 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 evidence9MProduction, tests, configuration, and documentation
Estimated implementation output9MImplementation, retries, integration, and verification
Engineering oversight717.0 hoursOrientation, integration, tests, and review
Active build time89.6 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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