Current repository readingScanned Jul 24, 2026, 5:03 PM UTC

flink-sql-runner Codebase Valuation

Dockerized runner, utilities, and functions for FlinkSQL applications

View DataSQRL/flink-sql-runner on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/DataSQRL

flink-sql-runner

Dockerized runner, utilities, and functions for FlinkSQL applications

RepoWorth$2,329Current measured development value · 1.4 active build days
Rebuild complexity87.58/100Profile: Complex
168.1K code tokens195 source filesJava primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/flink-sql-runner
Authored code168.1K tokens · 21,181 source lines
Complexity87.58/100 · Complex
Primary stackJava
Scan coverage100% · 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
$2,329

Modeled range $1,863 to $2,794

1.4 active build days11.1 engineering hours138.9K implementation tokens
Repository evidenceMeasured at the scanned commit
168.1K tokens

21,181 source lines across 195 authored files

55 test files2,228 dependencies100% 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$2,329
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity88/100Measured from code scale and structural signals
Maintainability72/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
#1velo@velo26864.4%Current GitHub contributor snapshot
#2ferenc-csaky@ferenc-csaky12129.1%Current GitHub contributor snapshot
#3mbroecheler@mbroecheler184.3%Current GitHub contributor snapshot
#4henneberger@henneberger61.4%Current GitHub contributor snapshot
#5mateczagany@mateczagany10.2%Current GitHub contributor snapshot
#6sap1ens@sap1ens10.2%Current GitHub contributor snapshot
#7raphaelauv@raphaelauv10.2%Current GitHub contributor snapshot
About flink-sql-runner

What the public repository appears to contain.

Dockerized runner, utilities, and functions for FlinkSQL applications

dockerflinkflinksqlkubernetes
License
NOASSERTION
Default branch
main
GitHub stars
31
Forks
5
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile751.2KB authored source
Java84.68%
XML12.15%
SQL2.2%
Shell0.97%
Source files195
Test files55
Manifests22
Dependencies2,228
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 signal72/100

Established based on deterministic repository structure and complexity signals.

Production source110.8K tokens

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

Test evidence57.3K tokens

55 detected test files contribute separately from production code.

Configuration and infrastructure0 tokens

22 manifests and 0 workspace boundaries were detected.

Documentation8.1K tokens

12 documentation files remain visible as a distinct enablement signal.

Integration surface2,243 signals

2,228 dependency declarations and 578 public-interface signals were measured.

Repository structure12 levels deep

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

Excluded from authored evidence0 files

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

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 evidence138.9KProduction, tests, configuration, and documentation
Estimated implementation output138.9KImplementation, retries, integration, and verification
Engineering oversight11.1 hoursOrientation, integration, tests, and review
Active build time1.4 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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