Current repository readingScanned Jul 25, 2026, 3:03 AM UTC

ESPresense Codebase Valuation

An ESP32 based node for gathering indoor positioning and transmitting to mqtt

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

ESPresense

An ESP32 based node for gathering indoor positioning and transmitting to mqtt

RepoWorth$3,630Current measured development value · 2.3 active build days
Rebuild complexity79.647/100Profile: Complex
305.7K code tokens123 source filesC primary language
Scanned Jul 25, 2026Public GitHub repositorycodevaluation.com/repoworth/espresense
Authored code305.7K tokens · 19,569 source lines
Complexity79.647/100 · Complex
Primary stackC
Scan coverage87.88% · 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,630

Modeled range $2,723 to $4,901

2.3 active build days18.1 engineering hours226.1K implementation tokens
Repository evidenceMeasured at the scanned commit
305.7K tokens

19,569 source lines across 123 authored files

9 test files25 dependencies87.88% scan coverage
Repository evidence

Building the historical and contribution view.

The headline RepoWorth and measured source facts are ready. Comparable history, accepted changes, and badge evidence will appear here as enrichment finishes.

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
#1cdheiser@cdheiser2100.0%Current GitHub contributor snapshot
About ESPresense

What the public repository appears to contain.

An ESP32 based node for gathering indoor positioning and transmitting to mqtt

esp32esp32-arduinohacktoberfesthome-assistanthome-automationhomeassistantindoor-positioningiotm5atomm5atom-litem5atom-matrixm5stickc-plus
License
AGPL-3.0
Default branch
main
GitHub stars
1,451
Forks
181
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile993KB authored source
C/C++66.41%
C++24.8%
TypeScript8.26%
CSS0.29%
Python0.11%
HTML0.08%
Shell0.05%
Source files123
Test files9
Manifests1
Dependencies25
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 signal63/100

Established based on deterministic repository structure and complexity signals.

Production source284.1K tokens

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

Test evidence21.6K tokens

9 detected test files contribute separately from production code.

Configuration and infrastructure1.3K tokens

1 manifests and 0 workspace boundaries were detected.

Documentation5.7K tokens

9 documentation files remain visible as a distinct enablement signal.

Integration surface63 signals

25 dependency declarations and 26 public-interface signals were measured.

Repository structure4 levels deep

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

Excluded from authored evidence0 files

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

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 evidence226.1KProduction, tests, configuration, and documentation
Estimated implementation output226.1KImplementation, retries, integration, and verification
Engineering oversight18.1 hoursOrientation, integration, tests, and review
Active build time2.3 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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