Current repository readingScanned Jul 24, 2026, 9:04 AM UTC

git-cliff Codebase Valuation

A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️

View orhun/git-cliff on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/orhun

git-cliff

A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️

RepoWorth$1,805Current measured development value · 1.1 active build days
Rebuild complexity89.805/100Profile: Complex
130.3K code tokens103 source filesRust primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/git-cliff
Authored code130.3K tokens · 15,538 source lines
Complexity89.805/100 · Complex
Primary stackRust
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
$1,805

Modeled range $1,444 to $2,166

1.1 active build days8.5 engineering hours106.4K implementation tokens
Repository evidenceMeasured at the scanned commit
130.3K tokens

15,538 source lines across 103 authored files

56 test files307 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$1,805
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity90/100Measured from code scale and structural signals
Maintainability56/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
#1orhun@orhun89288.8%Current GitHub contributor snapshot
#2ognis1205@ognis1205393.9%Current GitHub contributor snapshot
#3marcoieni@marcoieni151.5%Current GitHub contributor snapshot
#4nejcgalof@nejcgalof141.4%Current GitHub contributor snapshot
#5favna@favna121.2%Current GitHub contributor snapshot
#6kondanta@kondanta80.8%Current GitHub contributor snapshot
#7Cyclonit@Cyclonit70.7%Current GitHub contributor snapshot
#8joshka@joshka60.6%Current GitHub contributor snapshot
#9tessus@tessus60.6%Current GitHub contributor snapshot
#10bukowa@bukowa60.6%Current GitHub contributor snapshot
About git-cliff

What the public repository appears to contain.

A highly customizable Changelog Generator that follows Conventional Commit specifications ⛰️

changelogchangelog-generatorcommitconventional-changelogconventional-commitconventional-commitsgeneratorgitgit-cliffhacktoberfestkeepachangelogrust
License
Apache-2.0
Default branch
main
GitHub stars
12,036
Forks
307
Last public push
Jul 18, 2026
Repository state
Active public repository
Detected language profile548.4KB authored source
Rust86.73%
Shell6.06%
TypeScript3.43%
CSS1.69%
JavaScript1.08%
HTML1.02%
Source files103
Test files56
Manifests6
Dependencies307
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 signal56/100

Developing based on deterministic repository structure and complexity signals.

Production source119.6K tokens

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

Test evidence10.7K tokens

56 detected test files contribute separately from production code.

Configuration and infrastructure4.3K tokens

6 manifests and 0 workspace boundaries were detected.

Documentation106.5K tokens

157 documentation files remain visible as a distinct enablement signal.

Integration surface70 signals

307 dependency declarations and 11 public-interface signals were measured.

Repository structure4 levels deep

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

Excluded from authored evidence0 files

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

enablement

Documented foundation

At least 100,000 documentation tokens were measured in public documentation paths.

breadth

Polyglot system

At least five languages each represent one percent or more of measured source tokens.

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.

VerificationLow

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

What this valuation includes.

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