Current repository readingScanned Jul 24, 2026, 5:16 AM UTC

chromatic-e2e Codebase Valuation

Archive end-to-end tests to be replayed in Storybook and Chromatic

View chromaui/chromatic-e2e on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/chromaui

chromatic-e2e

Archive end-to-end tests to be replayed in Storybook and Chromatic

RepoWorth$1,366Current measured development value · Less than one active build day
Rebuild complexity75.746/100Profile: Complex
104.9K code tokens232 source filesTypeScript primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/chromatic-e2e
Authored code104.9K tokens · 13,378 source lines
Complexity75.746/100 · Complex
Primary stackTypeScript
Scan coverage96.21% · 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,366

Modeled range $1,093 to $1,639

0.9 active build days7.0 engineering hours86.9K implementation tokens
Repository evidenceMeasured at the scanned commit
104.9K tokens

13,378 source lines across 232 authored files

172 test files92 dependencies96.21% 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,366
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage96%current scan
Complexity76/100Measured from code scale and structural signals
Maintainability78/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
#1skitterm@skitterm44437.2%Current GitHub contributor snapshot
#2tevanoff@tevanoff29424.7%Current GitHub contributor snapshot
#3Ari Perkkiö@AriPerkkio15212.8%Current GitHub contributor snapshot
#4tmeasday@tmeasday13911.7%Current GitHub contributor snapshot
#5andrewortwein@andrewortwein615.1%Current GitHub contributor snapshot
#6thafryer@thafryer423.5%Current GitHub contributor snapshot
#7jwir3@jwir3242.0%Current GitHub contributor snapshot
#8ethriel3695@ethriel3695131.1%Current GitHub contributor snapshot
#9stephanie56@stephanie56121.0%Current GitHub contributor snapshot
#10ndelangen@ndelangen110.9%Current GitHub contributor snapshot
About chromatic-e2e

What the public repository appears to contain.

Archive end-to-end tests to be replayed in Storybook and Chromatic

License
MIT
Default branch
main
GitHub stars
27
Forks
12
Last public push
Jul 23, 2026
Repository state
Active public repository
Detected language profile413.6KB authored source
TypeScript89.23%
HTML8.17%
JavaScript2.42%
CSS0.18%
Source files232
Test files172
Manifests6
Dependencies92
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 source36.1K tokens

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

Test evidence68.8K tokens

172 detected test files contribute separately from production code.

Configuration and infrastructure5K tokens

6 manifests and 0 workspace boundaries were detected.

Documentation12.5K tokens

14 documentation files remain visible as a distinct enablement signal.

Integration surface879 signals

92 dependency declarations and 97 public-interface signals were measured.

Repository structure6 levels deep

0 large files and 941 branch signals add structural context.

Excluded from authored evidence0 files

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

quality

Verification depth

At least 20 percent of measured source tokens are in test paths.

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 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 evidence86.9KProduction, tests, configuration, and documentation
Estimated implementation output86.9KImplementation, retries, integration, and verification
Engineering oversight7.0 hoursOrientation, integration, tests, and review
Active build time0.9 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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