Current repository readingScanned Jul 25, 2026, 2:00 AM UTC

MitsubishiCN105ESPHome Codebase Valuation

ESPHome firmware inspired by GeoffDavis’s esphome-mitsubishiheatpump, directly integrating the SwiCago library within its codebase.

View echavet/MitsubishiCN105ESPHome on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/echavet

MitsubishiCN105ESPHome

ESPHome firmware inspired by GeoffDavis’s esphome-mitsubishiheatpump, directly integrating the SwiCago library within its codebase.

RepoWorth$1,169Current measured development value · Less than one active build day
Rebuild complexity69.38/100Profile: Complex
96.1K code tokens60 source filesC++ primary language
Scanned Jul 25, 2026Public GitHub repositorycodevaluation.com/repoworth/mitsubishicn105esphome
Authored code96.1K tokens · 10,462 source lines
Complexity69.38/100 · Complex
Primary stackC++
Scan coverage99.61% · 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
$1,169

Modeled range $934.83 to $1,402

0.8 active build days6.2 engineering hours77.1K implementation tokens
Repository evidenceMeasured at the scanned commit
96.1K tokens

10,462 source lines across 60 authored files

13 test files0 dependencies99.61% 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$1,169
Current measured reading
Measured · Jul 25, 2026Data through · Jul 25, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity69/100Measured from code scale and structural signals
Maintainability82/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
#1echavet@echavet50870.1%Current GitHub contributor snapshot
#2disruptivepatternmaterial@disruptivepatternmaterial12216.8%Current GitHub contributor snapshot
#3phidauex@phidauex314.3%Current GitHub contributor snapshot
#4ngist@ngist192.6%Current GitHub contributor snapshot
#5GioMez@GioMez141.9%Current GitHub contributor snapshot
#6calvindomenico@calvindomenico101.4%Current GitHub contributor snapshot
#7sanjay900@sanjay90071.0%Current GitHub contributor snapshot
#8theflu@theflu50.7%Current GitHub contributor snapshot
#9dkpnw@dkpnw50.7%Current GitHub contributor snapshot
#10ldotlopez@ldotlopez40.6%Current GitHub contributor snapshot
About MitsubishiCN105ESPHome

What the public repository appears to contain.

ESPHome firmware inspired by GeoffDavis’s esphome-mitsubishiheatpump, directly integrating the SwiCago library within its codebase.

License
Not detected
Default branch
main
GitHub stars
1,028
Forks
177
Last public push
Jul 2, 2026
Repository state
Active public repository
Detected language profile415.8KB authored source
C++64.55%
Python18.73%
C/C++16.72%
Source files60
Test files13
Manifests0
Dependencies0
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 signal82/100

Strong based on deterministic repository structure and complexity signals.

Production source75.3K tokens

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

Test evidence20.9K tokens

13 detected test files contribute separately from production code.

Configuration and infrastructure0 tokens

0 manifests and 0 workspace boundaries were detected.

Documentation24.8K tokens

6 documentation files remain visible as a distinct enablement signal.

Integration surface35 signals

0 dependency declarations and 0 public-interface signals were measured.

Repository structure3 levels deep

0 large files and 1,324 branch signals add structural context.

Excluded from authored evidence0 files

0 generated files were identified. Ignored and generated material does not inflate RepoWorth.

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.

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 evidence77.1KProduction, tests, configuration, and documentation
Estimated implementation output77.1KImplementation, retries, integration, and verification
Engineering oversight6.2 hoursOrientation, integration, tests, and review
Active build time0.8 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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