Current repository readingScanned Jul 24, 2026, 1:52 PM UTC
coven-cave Codebase Valuation
Cave is the native workspace for OpenCoven — a place to talk to your familiars, watch their tools, inspect their memory, and follow the work they're doing across sessions. A familiar isn't a chat window. It has a name, a purpose, a memory, a toolset, and, now, a home.
Cave is the native workspace for OpenCoven — a place to talk to your familiars, watch their tools, inspect their memory, and follow the work they're doing across sessions. A familiar isn't a chat window. It has a name, a purpose, a memory, a toolset, and, now, a home.
RepoWorth$74,372Current measured development value · 43.3 active build days
Rebuild complexity92.418/100Profile: Complex
5.5M code tokens2.8K source filesTypeScript primary language
Authored code5.5M tokens · 549,221 source lines
Complexity92.418/100 · Complex
Primary stackTypeScript
Scan coverage95.5% · 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$74,372
Modeled range $59,498 to $89,247
43.3 active build days346.2 engineering hours4.3M implementation tokens
Repository evidenceMeasured at the scanned commit5.5M tokens
549,221 source lines across 2,837 authored files
1,153 test files105 dependencies95.5% 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$74,372
Current measured reading
Measurement basisCurrent readingCurrent published repository scanEvidence coverage96%current scanComplexity92/100Measured from code scale and structural signalsMaintainability69/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.
Cave is the native workspace for OpenCoven — a place to talk to your familiars, watch their tools, inspect their memory, and follow the work they're doing across sessions. A familiar isn't a chat window. It has a name, a purpose, a memory, a toolset, and, now, a home.
License
NOASSERTION
Default branch
main
GitHub stars
19
Forks
20
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile21.5MB authored source
TypeScript78.42%
CSS10.61%
Swift4.16%
JavaScript2.82%
Rust1.41%
HTML1.29%
Python0.92%
Shell0.38%
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 signal69/100
Established based on deterministic repository structure and complexity signals.
Production source3.8M tokens
First-party implementation tokens eligible for the modeled code-scale input.
Test evidence1.7M tokens
1,153 detected test files contribute separately from production code.
Configuration and infrastructure5.5K tokens
2 manifests and 0 workspace boundaries were detected.
Documentation1.1M tokens
577 documentation files remain visible as a distinct enablement signal.
Integration surface19,672 signals
105 dependency declarations and 6,838 public-interface signals were measured.
Repository structure8 levels deep
0 large files and 100,944 branch signals add structural context.
Excluded from authored evidence0 files
10 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.
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.
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.
breadth
Polyglot system
At least five languages each represent one percent or more of measured source tokens.
enablement
Documentation atlas
More than one million measured documentation tokens support the public codebase.
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 evidence4.3MProduction, tests, configuration, and documentation
Estimated implementation output4.3MImplementation, retries, integration, and verification
Engineering oversight346.2 hoursOrientation, integration, tests, and review
Active build time43.3 daysModeled effort represented by the current source state
Evidence boundary
What this valuation includes.
CodeValuation.com counted supported authored source on commit ee159624e0444ad6de35a4c72ce2050cd031d033, measured deterministic repository signals, then estimated implementation, rework, testing, integration, and engineering oversight.
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.
