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

auv Codebase Valuation

๐Ÿ“ฑ๐Ÿญ No we are not computer use, it's Application Use Via... a unified orchestration layer of OS automation, 0 token cost

View moeru-ai/auv on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/moeru-ai

auv

๐Ÿ“ฑ๐Ÿญ No we are not computer use, it's Application Use Via... a unified orchestration layer of OS automation, 0 token cost

RepoWorth$23,425Current measured development value ยท 13.2 active build days
Rebuild complexity98.475/100Profile: Complex
1.6M code tokens714 source filesRust primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/auv
Authored code1.6M tokens ยท 189,902 source lines
Complexity98.475/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
$23,425

Modeled range $18,740 to $28,110

13.2 active build days105.7 engineering hours1.3M implementation tokens
Repository evidenceMeasured at the scanned commit
1.6M tokens

189,902 source lines across 714 authored files

11 test files969 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$23,425
Current measured reading
Measured ยท Jul 24, 2026Data through ยท Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity98/100Measured from code scale and structural signals
Maintainability46/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
#13361559784@336155978474071.8%Current GitHub contributor snapshot
#2nekomeowww@nekomeowww24323.6%Current GitHub contributor snapshot
#3sumimakito@sumimakito181.7%Current GitHub contributor snapshot
#4่—+85CD@kwaa151.5%Current GitHub contributor snapshot
#5PurCHES5@PurCHES570.7%Current GitHub contributor snapshot
#6luoling8192@luoling819240.4%Current GitHub contributor snapshot
#7Lilia-Chen@Lilia-Chen40.4%Current GitHub contributor snapshot
About auv

What the public repository appears to contain.

๐Ÿ“ฑ๐Ÿญ No we are not computer use, it's Application Use Via... a unified orchestration layer of OS automation, 0 token cost

agent-memoryagent-skillscomputer-usegui-automationos-automationphone-use
License
Apache-2.0
Default branch
main
GitHub stars
20
Forks
2
Last public push
Jul 23, 2026
Repository state
Active public repository
Detected language profile6.8MB authored source
Rust74.64%
JavaScript17.36%
TypeScript2.64%
Swift2.1%
HTML1.93%
CSS0.71%
Java0.32%
Python0.16%
Source files714
Test files11
Manifests41
Dependencies969
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 signal46/100

Developing based on deterministic repository structure and complexity signals.

Production source1.6M tokens

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

Test evidence18.8K tokens

11 detected test files contribute separately from production code.

Configuration and infrastructure8.1K tokens

41 manifests and 0 workspace boundaries were detected.

Documentation716K tokens

621 documentation files remain visible as a distinct enablement signal.

Integration surface775 signals

969 dependency declarations and 120 public-interface signals were measured.

Repository structure10 levels deep

0 large files and 20,336 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.

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.

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 evidence1.3MProduction, tests, configuration, and documentation
Estimated implementation output1.3MImplementation, retries, integration, and verification
Engineering oversight105.7 hoursOrientation, integration, tests, and review
Active build time13.2 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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