Current repository readingScanned Jul 24, 2026, 4:02 PM UTC

krkn Codebase Valuation

Chaos and resiliency testing tool for Kubernetes with a focus on improving performance under failure conditions. A CNCF sandbox project.

View krkn-chaos/krkn on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/krkn-chaos

krkn

Chaos and resiliency testing tool for Kubernetes with a focus on improving performance under failure conditions. A CNCF sandbox project.

RepoWorth$5,652Current measured development value · 3.6 active build days
Rebuild complexity74.82/100Profile: Complex
442.4K code tokens209 source filesPython primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/krkn
Authored code442.4K tokens · 52,891 source lines
Complexity74.82/100 · Complex
Primary stackPython
Scan coverage98.24% · 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,652

Modeled range $4,522 to $6,782

3.6 active build days28.9 engineering hours361.6K implementation tokens
Repository evidenceMeasured at the scanned commit
442.4K tokens

52,891 source lines across 209 authored files

90 test files46 dependencies98.24% 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,652
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage98%current scan
Complexity75/100Measured from code scale and structural signals
Maintainability79/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
#1paigerube14@paigerube1424436.1%Current GitHub contributor snapshot
#2chaitanyaenr@chaitanyaenr15823.4%Current GitHub contributor snapshot
#3tsebastiani@tsebastiani14621.6%Current GitHub contributor snapshot
#4sandrobonazzola@sandrobonazzola446.5%Current GitHub contributor snapshot
#5mffiedler@mffiedler203.0%Current GitHub contributor snapshot
#6yogananth-subramanian@yogananth-subramanian142.1%Current GitHub contributor snapshot
#7ddjain@ddjain131.9%Current GitHub contributor snapshot
#8sanjay7178@sanjay7178131.9%Current GitHub contributor snapshot
#9shahsahil264@shahsahil264131.9%Current GitHub contributor snapshot
#101PoPTRoN@1PoPTRoN101.5%Current GitHub contributor snapshot
About krkn

What the public repository appears to contain.

Chaos and resiliency testing tool for Kubernetes with a focus on improving performance under failure conditions. A CNCF sandbox project.

chaos-engineeringcontainerskubernetesperformancereliabilityresiliencyscalabilitytesting
License
Apache-2.0
Default branch
main
GitHub stars
484
Forks
234
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile2.1MB authored source
Python97.36%
Shell2.64%
Source files209
Test files90
Manifests0
Dependencies46
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 signal79/100

Strong based on deterministic repository structure and complexity signals.

Production source216.8K tokens

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

Test evidence225.5K tokens

90 detected test files contribute separately from production code.

Configuration and infrastructure0 tokens

0 manifests and 0 workspace boundaries were detected.

Documentation34.4K tokens

28 documentation files remain visible as a distinct enablement signal.

Integration surface1,414 signals

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

Repository structure4 levels deep

0 large files and 3,711 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.

architecture

Integration surface

At least 1,000 deterministic integration signals were measured in source.

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 evidence361.6KProduction, tests, configuration, and documentation
Estimated implementation output361.6KImplementation, retries, integration, and verification
Engineering oversight28.9 hoursOrientation, integration, tests, and review
Active build time3.6 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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