Current repository readingScanned Jul 24, 2026, 8:09 PM UTC
2026-lang-self-hosted-pi Codebase Valuation
A reproducible benchmark study comparing Go, Rust, Python, Node.js, and .NET on a Raspberry Pi 5 (ARM64), measuring throughput, latency, RAM footprint, startup time, binary size, and energy consumption across a shared CRUD HTTP API backed by SQLite.
A reproducible benchmark study comparing Go, Rust, Python, Node.js, and .NET on a Raspberry Pi 5 (ARM64), measuring throughput, latency, RAM footprint, startup time, binary size, and energy consumption across a shared CRUD HTTP API backed by SQLite.
RepoWorth$617.61Current measured development value · Less than one active build day
Rebuild complexity74.952/100Profile: Complex
49.3K code tokens27 source filesPython primary language
Authored code49.3K tokens · 5,297 source lines
Complexity74.952/100 · Complex
Primary stackPython
Scan coverage98.33% · 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$617.61
Modeled range $494.09 to $741.13
0.4 active build days3.2 engineering hours39.5K implementation tokens
Repository evidenceMeasured at the scanned commit49.3K tokens
5,297 source lines across 27 authored files
0 test files42 dependencies98.33% 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$617.61
Current measured reading
Measurement basisCurrent readingCurrent published repository scanEvidence coverage98%current scanComplexity75/100Measured from code scale and structural signalsMaintainability59/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.
A reproducible benchmark study comparing Go, Rust, Python, Node.js, and .NET on a Raspberry Pi 5 (ARM64), measuring throughput, latency, RAM footprint, startup time, binary size, and energy consumption across a shared CRUD HTTP API backed by SQLite.
License
MIT
Default branch
main
GitHub stars
1
Forks
0
Last public push
May 23, 2026
Repository state
Active public repository
Detected language profile195.8KB authored source
Python72.13%
Shell8.68%
C#5.47%
Rust5%
Go4.56%
Lua1.91%
JavaScript1.84%
MOD0.41%
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 signal59/100
Established based on deterministic repository structure and complexity signals.
Production source49.3K tokens
First-party implementation tokens eligible for the modeled code-scale input.
Test evidence0 tokens
0 detected test files contribute separately from production code.
Configuration and infrastructure183 tokens
3 manifests and 0 workspace boundaries were detected.
Documentation34.4K tokens
40 documentation files remain visible as a distinct enablement signal.
Integration surface80 signals
42 dependency declarations and 0 public-interface signals were measured.
Repository structure3 levels deep
0 large files and 701 branch signals add structural context.
Excluded from authored evidence0 files
1 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.
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 evidence39.5KProduction, tests, configuration, and documentation
Estimated implementation output39.5KImplementation, retries, integration, and verification
Engineering oversight3.2 hoursOrientation, integration, tests, and review
Active build time0.4 daysModeled effort represented by the current source state
Evidence boundary
What this valuation includes.
CodeValuation.com counted supported authored source on commit d1ba517deb5984030104209817fbc035d3923cc5, 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.
