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

custom-elements-manifest Codebase Valuation

Custom Elements Manifest is a file format that describes custom elements in your project.

View open-wc/custom-elements-manifest on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/open-wc

custom-elements-manifest

Custom Elements Manifest is a file format that describes custom elements in your project.

RepoWorth$25,719Current measured development value · 15.8 active build days
Rebuild complexity82.166/100Profile: Complex
2M code tokens143 source filesJavaScript primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/custom-elements-manifest
Authored code2M tokens · 212,377 source lines
Complexity82.166/100 · Complex
Primary stackJavaScript
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
$25,719

Modeled range $20,575 to $30,863

15.8 active build days126.4 engineering hours1.6M implementation tokens
Repository evidenceMeasured at the scanned commit
2M tokens

212,377 source lines across 143 authored files

68 test files42 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$25,719
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity82/100Measured from code scale and structural signals
Maintainability55/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
#1bennypowers@bennypowers6359.4%Current GitHub contributor snapshot
#2peschee@peschee109.4%Current GitHub contributor snapshot
#3tlouisse@tlouisse87.5%Current GitHub contributor snapshot
#4break-stuff@break-stuff65.7%Current GitHub contributor snapshot
#5daKmoR@daKmoR54.7%Current GitHub contributor snapshot
#6Kai-Richardson@Kai-Richardson43.8%Current GitHub contributor snapshot
#7ajmchambers@ajmchambers32.8%Current GitHub contributor snapshot
#8Matsuuu@Matsuuu32.8%Current GitHub contributor snapshot
#9muratcorlu@muratcorlu21.9%Current GitHub contributor snapshot
#10WickyNilliams@WickyNilliams21.9%Current GitHub contributor snapshot
About custom-elements-manifest

What the public repository appears to contain.

Custom Elements Manifest is a file format that describes custom elements in your project.

custom-elementscustom-elements-jsoncustom-elements-manifestcustomelementscustomelementsjsoncustomelementsmanifesthacktoberfestmanifestopen-wcweb-componentswebcomponents
License
Not detected
Default branch
master
GitHub stars
320
Forks
63
Last public push
Jul 3, 2026
Repository state
Active public repository
Detected language profile9.9MB authored source
JavaScript99.78%
TypeScript0.13%
CSS0.09%
HTML0.01%
Source files143
Test files68
Manifests16
Dependencies42
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 signal55/100

Developing based on deterministic repository structure and complexity signals.

Production source2M tokens

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

Test evidence10.3K tokens

68 detected test files contribute separately from production code.

Configuration and infrastructure2.3K tokens

16 manifests and 0 workspace boundaries were detected.

Documentation82.1K tokens

77 documentation files remain visible as a distinct enablement signal.

Integration surface756 signals

42 dependency declarations and 274 public-interface signals were measured.

Repository structure10 levels deep

0 large files and 55,212 branch signals add structural context.

Excluded from authored evidence0 files

24 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 scaleHigh

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 evidence1.6MProduction, tests, configuration, and documentation
Estimated implementation output1.6MImplementation, retries, integration, and verification
Engineering oversight126.4 hoursOrientation, integration, tests, and review
Active build time15.8 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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