Current repository readingScanned Jul 25, 2026, 4:58 AM UTC

CylindricalGeometryCorrection Codebase Valuation

This library produces a FITS with the cylindrical geometry corrected (hollow or not)

View ornlneutronimaging/CylindricalGeometryCorrection on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/ornlneutronimaging

CylindricalGeometryCorrection

This library produces a FITS with the cylindrical geometry corrected (hollow or not)

RepoWorth$229.45Current measured development value · Less than one active build day
Rebuild complexity72.56/100Profile: Complex
18.1K code tokens7 source filesPython primary language
Scanned Jul 25, 2026Public GitHub repositorycodevaluation.com/repoworth/cylindricalgeometrycorrection
Authored code18.1K tokens · 2,201 source lines
Complexity72.56/100 · Complex
Primary stackPython
Scan coverage99.45% · 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
$229.45

Modeled range $183.56 to $275.34

0.1 active build days1.2 engineering hours14.9K implementation tokens
Repository evidenceMeasured at the scanned commit
18.1K tokens

2,201 source lines across 7 authored files

4 test files225 dependencies99.45% scan coverage
Repository evidence

Building the historical and contribution view.

The headline RepoWorth and measured source facts are ready. Comparable history, accepted changes, and badge evidence will appear here as enrichment finishes.

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
#1Chen Zhang@KedoKudo94100.0%Current GitHub contributor snapshot
About CylindricalGeometryCorrection

What the public repository appears to contain.

This library produces a FITS with the cylindrical geometry corrected (hollow or not)

License
BSD-3-Clause
Default branch
next
GitHub stars
1
Forks
0
Last public push
Jul 21, 2026
Repository state
Active public repository
Detected language profile81.9KB authored source
Python100%
Source files7
Test files4
Manifests1
Dependencies225
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 signal78/100

Strong based on deterministic repository structure and complexity signals.

Production source7.8K tokens

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

Test evidence10.3K tokens

4 detected test files contribute separately from production code.

Configuration and infrastructure2.9K tokens

1 manifests and 0 workspace boundaries were detected.

Documentation5.2K tokens

9 documentation files remain visible as a distinct enablement signal.

Integration surface46 signals

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

Repository structure2 levels deep

0 large files and 201 branch signals add structural context.

Excluded from authored evidence0 files

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

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 evidence14.9KProduction, tests, configuration, and documentation
Estimated implementation output14.9KImplementation, retries, integration, and verification
Engineering oversight1.2 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 40eeec84ff7c4a77154d15d06fd12541181e9db9, 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.