Current repository valuation
Know what the visible codebase would cost to rebuild today.
RepoWorth measures authored code at one identified commit and produces a current development-value estimate with the code footprint, complexity, coverage, and valuation components attached.
It is a repository valuation, not a company valuation, transaction price, or score for the people who built it.
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.
Run RepoWorth
Value a public GitHub repository.
Paste an open source repository URL. If GitHub cannot reach it publicly, we’ll direct you to sign in and connect read-only private access.
A valuation should explain the code, not hide behind one number.
RepoWorth connects the estimate to the current source corpus, implementation difficulty, verification surface, development effort, and delivery-risk allowance. A reader can see what increased the estimate, what was excluded, and where evidence is incomplete.
The result is only useful if you can see what produced it.
Authored source footprint
Counts supported source and test tokens while excluding dependencies, generated output, binaries, lockfiles, and other non-authored material.
Implementation difficulty
Uses repository scale, language mix, branch density, architecture breadth, dependencies, workspaces, and large-file pressure to describe reconstruction difficulty.
Tests and documentation
Reports the visible verification and enablement surface as repository evidence without claiming that tests pass or that documentation is complete.
Expert delivery work
Separates implementation output from the senior engineering time needed to orient, steer, integrate, verify, review, and release the work.
Valuation components
Shows the direct components, current estimate, and bounded range so the headline RepoWorth can be reconciled rather than accepted on faith.
Commit and coverage
Records the repository, default branch, exact cutoff commit, scan time, corpus size, coverage, and data-quality warnings behind the result.
From repository evidence to a readable record.
Identify the current repository
Resolve the public default branch and freeze the exact commit used for the result.
Measure the authored codebase
Classify the corpus, count supported code, and calculate the current structural and verification evidence.
Reconcile and publish
Calculate RepoWorth, preserve the inputs and boundaries, and create a shareable repository record.
One evidence base, read from the right perspective.
Understand what exists now.
Use RepoWorth to establish a current technical baseline before discussing delivery, staffing, refactoring, or roadmap scope.
- Visible valuation components
- Current complexity and verification posture
- Shareable evidence page
Start diligence with a reproducible baseline.
Use the current repository record as one technical input alongside commercial, operational, security, and legal diligence.
- Identified commit and coverage
- Current development-value estimate
- Explicit decision boundaries
Clear evidence boundaries are part of the product.
RepoWorth does not value revenue, customers, brand, distribution, proprietary data, market position, or the operating company.
It does not establish ownership, freedom to operate, licensing compliance, patentability, or transaction consideration.
It estimates current reconstruction value from the visible codebase; it does not reconstruct every hour or dollar previously spent.
Questions
What to know before reading a RepoWorth result.
RepoWorth is most useful when its repository scope, evidence, and limits travel with the number.
What does RepoWorth value?
RepoWorth estimates the current development value of the visible authored code at an identified commit. It does not value the company, revenue, customers, brand, intellectual-property rights, or the people who built it.
Does the scan store repository source code?
No. Code is evaluated in real time directly from GitHub and is never stored. Derived measurements, the evaluated commit, and valuation history are saved so the result remains reviewable.
Can I scan a private repository?
Yes. Public repositories require no signup. Private repositories require a free trial and authorized, read-only GitHub access so the repository can be evaluated without exposing its source in the report.
Why can RepoWorth change over time?
The visible codebase, structural evidence, verification surface, dependencies, and measured coverage can change as new work reaches the default branch. Each result identifies its cutoff commit so two readings can be compared on a known basis.
Start with the current codebase
Create the baseline every later report can build on.
Run RepoWorth for a public GitHub repository and inspect the evidence behind the estimate.
Calculate RepoWorth
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.