Kedro is a toolbox for production-ready data science. It uses software engineering best practices to help you create data engineering and data science pipelines that are reproducible, maintainable, and modular.
View kedro-org/kedro on GitHubKedro is a toolbox for production-ready data science. It uses software engineering best practices to help you create data engineering and data science pipelines that are reproducible, maintainable, and modular.
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.
Modeled range $4,349 to $6,524
48,708 source lines across 209 authored files
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.
This current scan establishes the RepoWorth baseline. Comparable value changes appear only after another completed scan under the same measurement basis.
Commit activity provides delivery context. It does not assign a historical RepoWorth to unscanned commits or treat commit count as value.
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.
Ranked from the public GitHub contributor evidence available at the latest scan. This table describes measured repository activity, not ownership or original authorship.
| Rank | Contributor | Contributions | Share of top group | Latest measured activity |
|---|---|---|---|---|
| #1 |  merelcht@merelcht | 363 | 21.7% | Current GitHub contributor snapshot |
| #2 |  ElenaKhaustova@ElenaKhaustova | 188 | 11.2% | Current GitHub contributor snapshot |
| #3 |  deepyaman@deepyaman | 175 | 10.4% | Current GitHub contributor snapshot |
| #4 |  idanov@idanov | 173 | 10.3% | Current GitHub contributor snapshot |
| #5 |  ankatiyar@ankatiyar | 160 | 9.6% | Current GitHub contributor snapshot |
| #6 |  noklam@noklam | 153 | 9.1% | Current GitHub contributor snapshot |
| #7 |  921kiyo@921kiyo | 123 | 7.3% | Current GitHub contributor snapshot |
| #8 |  limdauto@limdauto | 120 | 7.2% | Current GitHub contributor snapshot |
| #9 |  antonymilne@antonymilne | 112 | 6.7% | Current GitHub contributor snapshot |
| #10 |  stichbury@stichbury | 108 | 6.4% | Current GitHub contributor snapshot |
Kedro is a toolbox for production-ready data science. It uses software engineering best practices to help you create data engineering and data science pipelines that are reproducible, maintainable, and modular.
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.
Established based on deterministic repository structure and complexity signals.
First-party implementation tokens eligible for the modeled code-scale input.
87 detected test files contribute separately from production code.
4 manifests and 0 workspace boundaries were detected.
177 documentation files remain visible as a distinct enablement signal.
383 dependency declarations and 0 public-interface signals were measured.
0 large files and 3,273 branch signals add structural context.
13 generated files were identified. Ignored and generated material does not inflate RepoWorth.
Each highlight records a measured characteristic of the same repository scan used for this RepoWorth report.
At least 100,000 documentation tokens were measured in public documentation paths.
At least 1,000 deterministic integration signals were measured in source.
At least 20 percent of measured source tokens are in test paths.
At least 35 percent of measured source tokens are in detected test paths.
Code scale, branching, dependencies, languages, structure, and visible test evidence shape the implementation and verification effort represented by this repository.
Measured from the current source archive.
Derived from branch density, dependencies, languages, and code scale.
Measures visible test code relative to the source corpus.
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.
CodeValuation.com counted supported authored source on commit 72cef2cdde9d072444c6a7280ae74ba752dafeb6, measured deterministic repository signals, then estimated implementation, rework, testing, integration, and engineering oversight.
Supported first-party source, tests, configuration, manifests, repository structure, dependency signals, and framework boundaries.
Common generated and vendored files, build output, dependencies, lockfiles, minified assets, binaries, media, and private systems outside this repository.
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.
Enter a public GitHub URL to create a current repository reading.