Current repository readingScanned Jul 24, 2026, 9:53 AM UTC

gitcrawl Codebase Valuation

Local-first GitHub issue and pull request crawler for maintainer triage

View openclaw/gitcrawl on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/openclaw

gitcrawl

Local-first GitHub issue and pull request crawler for maintainer triage

RepoWorth$9,211Current measured development value · 5.7 active build days
Rebuild complexity80.919/100Profile: Complex
700.7K code tokens140 source filesGo primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/gitcrawl
Authored code700.7K tokens · 81,543 source lines
Complexity80.919/100 · Complex
Primary stackGo
Scan coverage89.05% · 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
$9,211

Modeled range $6,908 to $12,434

5.7 active build days45.6 engineering hours569.6K implementation tokens
Repository evidenceMeasured at the scanned commit
700.7K tokens

81,543 source lines across 140 authored files

65 test files50 dependencies89.05% 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$9,211
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage89%current scan
Complexity81/100Measured from code scale and structural signals
Maintainability75/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
#1Vincent Koc@vincentkoc42264.4%Current GitHub contributor snapshot
#2Peter Steinberger@steipete20631.5%Current GitHub contributor snapshot
#3Andy Ye@TurboTheTurtle121.8%Current GitHub contributor snapshot
#4Dallin Romney@RomneyDa71.1%Current GitHub contributor snapshot
#5joshka@joshka20.3%Current GitHub contributor snapshot
#6stain lu@stainlu20.3%Current GitHub contributor snapshot
#7Hannes Rudolph@hannesrudolph10.2%Current GitHub contributor snapshot
#8Altay@altaywtf10.2%Current GitHub contributor snapshot
#9AmAzing129@AmAzing12910.2%Current GitHub contributor snapshot
#10GongYuanCaiJi@GongYuanCaiJi10.2%Current GitHub contributor snapshot
About gitcrawl

What the public repository appears to contain.

Local-first GitHub issue and pull request crawler for maintainer triage

License
MIT
Default branch
main
GitHub stars
99
Forks
26
Last public push
Jul 23, 2026
Repository state
Active public repository
Detected language profile2.7MB authored source
Go90.6%
Python7.66%
SQL1.06%
Shell0.6%
MOD0.08%
Source files140
Test files65
Manifests1
Dependencies50
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 signal75/100

Strong based on deterministic repository structure and complexity signals.

Production source262.3K tokens

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

Test evidence438.4K tokens

65 detected test files contribute separately from production code.

Configuration and infrastructure0 tokens

1 manifests and 0 workspace boundaries were detected.

Documentation52.8K tokens

27 documentation files remain visible as a distinct enablement signal.

Integration surface353 signals

50 dependency declarations and 11 public-interface signals were measured.

Repository structure4 levels deep

0 large files and 14,495 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.

quality

Verification depth

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

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 evidence569.6KProduction, tests, configuration, and documentation
Estimated implementation output569.6KImplementation, retries, integration, and verification
Engineering oversight45.6 hoursOrientation, integration, tests, and review
Active build time5.7 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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