Current repository readingScanned Jul 24, 2026, 2:05 PM UTC

nanogit Codebase Valuation

Lightweight, HTTPS-only Git client library for Go, built for cloud-native and multitenant services

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

nanogit

Lightweight, HTTPS-only Git client library for Go, built for cloud-native and multitenant services

RepoWorth$5,940Current measured development value · 3.5 active build days
Rebuild complexity91.548/100Profile: Complex
424.9K code tokens195 source filesGo primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/nanogit
Authored code424.9K tokens · 50,711 source lines
Complexity91.548/100 · Complex
Primary stackGo
Scan coverage98.01% · 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
$5,940

Modeled range $4,752 to $7,128

3.5 active build days27.8 engineering hours347.2K implementation tokens
Repository evidenceMeasured at the scanned commit
424.9K tokens

50,711 source lines across 195 authored files

98 test files263 dependencies98.01% 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$5,940
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage98%current scan
Complexity92/100Measured from code scale and structural signals
Maintainability68/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
#1Roberto Jiménez Sánchez@MissingRoberto21788.2%Current GitHub contributor snapshot
#2Alejandro@amalavet124.9%Current GitHub contributor snapshot
#3Daniele Stefano Ferru@ferruvich114.5%Current GitHub contributor snapshot
#4Mariell Hoversholm@Proximyst20.8%Current GitHub contributor snapshot
#5Ryan McKinley@ryantxu20.8%Current GitHub contributor snapshot
#6karimzakzouk@karimzakzouk10.4%Current GitHub contributor snapshot
#7omkar-sarswat@omkar-sarswat10.4%Current GitHub contributor snapshot
About nanogit

What the public repository appears to contain.

Lightweight, HTTPS-only Git client library for Go, built for cloud-native and multitenant services

cloud-nativegitgit-protocolgitopsgogolanggrafana
License
Apache-2.0
Default branch
main
GitHub stars
46
Forks
3
Last public push
Jul 23, 2026
Repository state
Active public repository
Detected language profile1.7MB authored source
Go98.83%
MOD0.75%
Python0.23%
Shell0.14%
TypeScript0.03%
CSS0.02%
Source files195
Test files98
Manifests6
Dependencies263
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 signal68/100

Established based on deterministic repository structure and complexity signals.

Production source166.3K tokens

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

Test evidence258.6K tokens

98 detected test files contribute separately from production code.

Configuration and infrastructure242 tokens

6 manifests and 0 workspace boundaries were detected.

Documentation54.5K tokens

32 documentation files remain visible as a distinct enablement signal.

Integration surface243 signals

263 dependency declarations and 2 public-interface signals were measured.

Repository structure3 levels deep

0 large files and 4,518 branch signals add structural context.

Excluded from authored evidence0 files

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

quality

Verification depth

At least 20 percent of measured source tokens are in test paths.

quality

Test fortress

At least 35 percent of measured source tokens are in detected test paths.

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 evidence347.2KProduction, tests, configuration, and documentation
Estimated implementation output347.2KImplementation, retries, integration, and verification
Engineering oversight27.8 hoursOrientation, integration, tests, and review
Active build time3.5 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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