Current repository readingScanned Jul 25, 2026, 9:01 AM UTC

k8s-network-node-labeller Codebase Valuation

Discovers AMD AINIC's characteristics and labels Kubernetes nodes with the corresponding information

View ROCm/k8s-network-node-labeller on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/ROCm

k8s-network-node-labeller

Discovers AMD AINIC's characteristics and labels Kubernetes nodes with the corresponding information

RepoWorth$645.13Current measured development value · Less than one active build day
Rebuild complexity75.983/100Profile: Complex
48.2K code tokens41 source filesGo primary language
Scanned Jul 25, 2026Public GitHub repositorycodevaluation.com/repoworth/k8s-network-node-labeller
Authored code48.2K tokens · 6,898 source lines
Complexity75.983/100 · Complex
Primary stackGo
Scan coverage92.68% · 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
$645.13

Modeled range $516.10 to $774.16

0.4 active build days3.3 engineering hours41K implementation tokens
Repository evidenceMeasured at the scanned commit
48.2K tokens

6,898 source lines across 41 authored files

17 test files144 dependencies92.68% 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
#1shiv-tyagi@shiv-tyagi58100.0%Current GitHub contributor snapshot
About k8s-network-node-labeller

What the public repository appears to contain.

Discovers AMD AINIC's characteristics and labels Kubernetes nodes with the corresponding information

License
Apache-2.0
Default branch
main
GitHub stars
1
Forks
4
Last public push
Jun 3, 2026
Repository state
Active public repository
Detected language profile194.3KB authored source
Go97.5%
MOD1.21%
Shell0.77%
Python0.53%
Source files41
Test files17
Manifests1
Dependencies144
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 signal58/100

Established based on deterministic repository structure and complexity signals.

Production source19.6K tokens

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

Test evidence28.6K tokens

17 detected test files contribute separately from production code.

Configuration and infrastructure0 tokens

1 manifests and 0 workspace boundaries were detected.

Documentation5.5K tokens

8 documentation files remain visible as a distinct enablement signal.

Integration surface40 signals

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

Repository structure9 levels deep

0 large files and 759 branch signals add structural context.

Excluded from authored evidence0 files

3,382 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 evidence41KProduction, tests, configuration, and documentation
Estimated implementation output41KImplementation, retries, integration, and verification
Engineering oversight3.3 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 923847dac9f3058bf0ab823b184c39899237ad15, 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.