Current repository readingScanned Jul 24, 2026, 11:55 AM UTC

HomeClaw Codebase Valuation

HomeKit smart home control via MCP — lights, locks, thermostats, and scenes for Claude Desktop, Claude Code, and OpenClaw

View omarshahine/HomeClaw on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/omarshahine

HomeClaw

HomeKit smart home control via MCP — lights, locks, thermostats, and scenes for Claude Desktop, Claude Code, and OpenClaw

RepoWorth$3,037Current measured development value · 1.9 active build days
Rebuild complexity77.231/100Profile: Complex
237.6K code tokens101 source filesSwift primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/homeclaw
Authored code237.6K tokens · 26,595 source lines
Complexity77.231/100 · Complex
Primary stackSwift
Scan coverage85.78% · 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
$3,037

Modeled range $2,278 to $4,100

1.9 active build days15.3 engineering hours191.7K implementation tokens
Repository evidenceMeasured at the scanned commit
237.6K tokens

26,595 source lines across 101 authored files

8 test files12 dependencies85.78% 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$3,037
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage86%current scan
Complexity77/100Measured from code scale and structural signals
Maintainability55/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
#1Omar Shahine@omarshahine22694.2%Current GitHub contributor snapshot
#2carlmidson@carlmidson62.5%Current GitHub contributor snapshot
#3claude@claude20.8%Current GitHub contributor snapshot
#4Obbut@Obbut20.8%Current GitHub contributor snapshot
#5desimone@desimone10.4%Current GitHub contributor snapshot
#6nitaybz@nitaybz10.4%Current GitHub contributor snapshot
#7bryangauvin@bryangauvin10.4%Current GitHub contributor snapshot
#8rieckt@rieckt10.4%Current GitHub contributor snapshot
About HomeClaw

What the public repository appears to contain.

HomeKit smart home control via MCP — lights, locks, thermostats, and scenes for Claude Desktop, Claude Code, and OpenClaw

claudehomekitmacosmcpsmart-homeswift
License
MIT
Default branch
main
GitHub stars
150
Forks
22
Last public push
Jul 18, 2026
Repository state
Active public repository
Detected language profile1MB authored source
Swift78.86%
Python12.81%
Shell4.36%
JavaScript2.39%
TypeScript1.57%
Other0.01%
Source files101
Test files8
Manifests5
Dependencies12
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 signal55/100

Developing based on deterministic repository structure and complexity signals.

Production source222.5K tokens

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

Test evidence15.1K tokens

8 detected test files contribute separately from production code.

Configuration and infrastructure827 tokens

5 manifests and 0 workspace boundaries were detected.

Documentation169.5K tokens

137 documentation files remain visible as a distinct enablement signal.

Integration surface612 signals

12 dependency declarations and 20 public-interface signals were measured.

Repository structure5 levels deep

0 large files and 6,493 branch signals add structural context.

Excluded from authored evidence0 files

8 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.

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 scaleModerate

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 evidence191.7KProduction, tests, configuration, and documentation
Estimated implementation output191.7KImplementation, retries, integration, and verification
Engineering oversight15.3 hoursOrientation, integration, tests, and review
Active build time1.9 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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