Current repository readingScanned Jul 24, 2026, 7:09 PM UTC

kestra Codebase Valuation

Event Driven Orchestration & Scheduling Platform for Mission Critical Applications

View kestra-io/kestra on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/kestra-io

kestra

Event Driven Orchestration & Scheduling Platform for Mission Critical Applications

RepoWorth$53,109Current measured development value · 29.7 active build days
Rebuild complexity100/100Profile: Complex
3.7M code tokens3.7K source filesJava primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/kestra
Authored code3.7M tokens · 426,659 source lines
Complexity100/100 · Complex
Primary stackJava
Scan coverage96.63% · 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
$53,109

Modeled range $42,487 to $63,731

29.7 active build days237.9 engineering hours3M implementation tokens
Repository evidenceMeasured at the scanned commit
3.7M tokens

426,659 source lines across 3,697 authored files

1,142 test files1,584 dependencies96.63% 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$53,109
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage97%current scan
Complexity100/100Measured from code scale and structural signals
Maintainability64/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.

52-week repository activity

5,019 commits across the public default-branch history.

Commit activity provides delivery context. It does not assign a historical RepoWorth to unscanned commits or treat commit count as value.

Jul 27, 2025Weekly commitsJul 19, 2026

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
#1tchiotludo@tchiotludo1,80922.0%Current GitHub contributor snapshot
#2loicmathieu@loicmathieu1,69220.6%Current GitHub contributor snapshot
#3MilosPaunovic@MilosPaunovic96611.8%Current GitHub contributor snapshot
#4brian-mulier-p@brian-mulier-p94311.5%Current GitHub contributor snapshot
#5Skraye@Skraye7469.1%Current GitHub contributor snapshot
#6fhussonnois@fhussonnois5546.8%Current GitHub contributor snapshot
#7elevatebart@elevatebart5446.6%Current GitHub contributor snapshot
#8Piyush-r-bhaskar@Piyush-r-bhaskar4675.7%Current GitHub contributor snapshot
#9AcevedoR@AcevedoR2723.3%Current GitHub contributor snapshot
#10anna-geller@anna-geller2142.6%Current GitHub contributor snapshot
About kestra

What the public repository appears to contain.

Event Driven Orchestration & Scheduling Platform for Mission Critical Applications

ai-agentsautomationcontrol-planedata-engineeringdata-orchestrationdata-orchestratordevopsetlhacktoberfesthigh-availabilityinfra-automationinfra-ops
License
Apache-2.0
Default branch
develop
GitHub stars
27,455
Forks
2,755
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile16MB authored source
Java63.26%
TypeScript18.17%
Vue16.22%
SQL0.88%
JavaScript0.51%
SCSS0.41%
GRADLE0.39%
Shell0.11%
Source files3,697
Test files1,142
Manifests29
Dependencies1,584
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 signal64/100

Established based on deterministic repository structure and complexity signals.

Production source2.2M tokens

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

Test evidence1.4M tokens

1,142 detected test files contribute separately from production code.

Configuration and infrastructure10.2K tokens

29 manifests and 0 workspace boundaries were detected.

Documentation44.1K tokens

25 documentation files remain visible as a distinct enablement signal.

Integration surface39,357 signals

1,584 dependency declarations and 8,172 public-interface signals were measured.

Repository structure12 levels deep

0 large files and 34,526 branch signals add structural context.

Excluded from authored evidence0 files

57 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

Interface builder

At least 500 deterministic public interface signals were measured in source.

architecture

Integration mesh

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

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.

architecture

Dependency ecosystem

At least 500 dependency declarations were measured across supported manifests.

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 evidence3MProduction, tests, configuration, and documentation
Estimated implementation output3MImplementation, retries, integration, and verification
Engineering oversight237.9 hoursOrientation, integration, tests, and review
Active build time29.7 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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