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

github-datasource Codebase Valuation

The GitHub data source lets you visualize GitHub data in Grafana dashboards

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

github-datasource

The GitHub data source lets you visualize GitHub data in Grafana dashboards

RepoWorth$1,688Current measured development value · 1.0 active build days
Rebuild complexity82.697/100Profile: Complex
123.7K code tokens180 source filesGo primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/github-datasource
Authored code123.7K tokens · 16,390 source lines
Complexity82.697/100 · Complex
Primary stackGo
Scan coverage98.95% · 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,688

Modeled range $1,350 to $2,025

1.0 active build days8.3 engineering hours103.4K implementation tokens
Repository evidenceMeasured at the scanned commit
123.7K tokens

16,390 source lines across 180 authored files

37 test files191 dependencies98.95% 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,688
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage99%current scan
Complexity83/100Measured from code scale and structural signals
Maintainability74/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
#1Kevin Minehart Tenorio@kminehart10038.8%Current GitHub contributor snapshot
#2Ivana Huckova@ivanahuckova3413.2%Current GitHub contributor snapshot
#3Andreas Christou@aangelisc3112.0%Current GitHub contributor snapshot
#4Zoltán Bedi@zoltanbedi2710.5%Current GitHub contributor snapshot
#5Sriram@yesoreyeram249.3%Current GitHub contributor snapshot
#6Jocelyn Collado-Kuri@jcolladokuri124.7%Current GitHub contributor snapshot
#7ismail simsek@itsmylife124.7%Current GitHub contributor snapshot
#8Gareth@itsgareth72.7%Current GitHub contributor snapshot
#9Gábor Farkas@gabor62.3%Current GitHub contributor snapshot
#10Scott Lepper@scottlepp51.9%Current GitHub contributor snapshot
About github-datasource

What the public repository appears to contain.

The GitHub data source lets you visualize GitHub data in Grafana dashboards

group-datasources
License
Apache-2.0
Default branch
main
GitHub stars
306
Forks
69
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile502.4KB authored source
Go77.22%
TypeScript20.01%
MOD1.36%
JavaScript0.88%
Shell0.53%
Source files180
Test files37
Manifests2
Dependencies191
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 signal74/100

Established based on deterministic repository structure and complexity signals.

Production source84.3K tokens

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

Test evidence39.4K tokens

37 detected test files contribute separately from production code.

Configuration and infrastructure4K tokens

2 manifests and 0 workspace boundaries were detected.

Documentation23.2K tokens

11 documentation files remain visible as a distinct enablement signal.

Integration surface571 signals

191 dependency declarations and 84 public-interface signals were measured.

Repository structure3 levels deep

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

Excluded from authored evidence0 files

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

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

What this valuation includes.

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