Current repository readingScanned Jul 24, 2026, 3:58 PM UTC

airflow-clickhouse-plugin Codebase Valuation

The most popular ClickHouse plugin for Airflow. ๐Ÿ” Top-1% downloads on PyPI: https://pypi.org/project/airflow-clickhouse-plugin! Based on mymarilyn/clickhouse-driver.

View bryzgaloff/airflow-clickhouse-plugin on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/bryzgaloff

airflow-clickhouse-plugin

The most popular ClickHouse plugin for Airflow. ๐Ÿ” Top-1% downloads on PyPI: https://pypi.org/project/airflow-clickhouse-plugin! Based on mymarilyn/clickhouse-driver.

RepoWorth$113.31Current measured development value ยท Less than one active build day
Rebuild complexity57.489/100Profile: Complex
9.5K code tokens18 source filesPython primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/airflow-clickhouse-plugin
Authored code9.5K tokens ยท 1,336 source lines
Complexity57.489/100 ยท Complex
Primary stackPython
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
$113.31

Modeled range $90.65 to $135.97

0.1 active build days0.6 engineering hours8K implementation tokens
Repository evidenceMeasured at the scanned commit
9.5K tokens

1,336 source lines across 18 authored files

12 test files48 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$113.31
Current measured reading
Measured ยท Jul 24, 2026Data through ยท Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity57/100Measured from code scale and structural signals
Maintainability88/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
#1bryzgaloff@bryzgaloff28887.3%Current GitHub contributor snapshot
#2r3b-fish@r3b-fish144.2%Current GitHub contributor snapshot
#3dolfinus@dolfinus61.8%Current GitHub contributor snapshot
#4ne1r0n@ne1r0n51.5%Current GitHub contributor snapshot
#5viktortnk@viktortnk30.9%Current GitHub contributor snapshot
#6GaMeRaM@GaMeRaM30.9%Current GitHub contributor snapshot
#7alexander-chashnikov@alexander-chashnikov30.9%Current GitHub contributor snapshot
#8CorsettiS@CorsettiS30.9%Current GitHub contributor snapshot
#9dparmon@dparmon30.9%Current GitHub contributor snapshot
#10bobelev@bobelev20.6%Current GitHub contributor snapshot
About airflow-clickhouse-plugin

What the public repository appears to contain.

The most popular ClickHouse plugin for Airflow. ๐Ÿ” Top-1% downloads on PyPI: https://pypi.org/project/airflow-clickhouse-plugin! Based on mymarilyn/clickhouse-driver.

airflowclickhousepythonpython3
License
MIT
Default branch
master
GitHub stars
184
Forks
46
Last public push
Jul 20, 2026
Repository state
Active public repository
Detected language profile44.2KB authored source
Python100%
Source files18
Test files12
Manifests1
Dependencies48
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 signal88/100

Strong based on deterministic repository structure and complexity signals.

Production source2.6K tokens

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

Test evidence6.8K tokens

12 detected test files contribute separately from production code.

Configuration and infrastructure419 tokens

1 manifests and 0 workspace boundaries were detected.

Documentation6.1K tokens

1 documentation files remain visible as a distinct enablement signal.

Integration surface59 signals

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

Repository structure3 levels deep

0 large files and 43 branch signals add structural context.

Excluded from authored evidence0 files

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

ComplexityModerate

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 evidence8KProduction, tests, configuration, and documentation
Estimated implementation output8KImplementation, retries, integration, and verification
Engineering oversight0.6 hoursOrientation, integration, tests, and review
Active build time0.1 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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