Current repository readingScanned Jul 24, 2026, 2:37 AM UTC

lightningcss Codebase Valuation

An extremely fast CSS parser, transformer, bundler, and minifier written in Rust.

View parcel-bundler/lightningcss on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/parcel-bundler

lightningcss

An extremely fast CSS parser, transformer, bundler, and minifier written in Rust.

RepoWorth$11,767Current measured development value · 6.7 active build days
Rebuild complexity96.008/100Profile: Complex
809.6K code tokens171 source filesRust primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/lightningcss
Authored code809.6K tokens · 104,292 source lines
Complexity96.008/100 · Complex
Primary stackRust
Scan coverage91.64% · 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
$11,767

Modeled range $9,414 to $14,121

6.7 active build days53.8 engineering hours672.2K implementation tokens
Repository evidenceMeasured at the scanned commit
809.6K tokens

104,292 source lines across 171 authored files

12 test files293 dependencies91.64% 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$11,767
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage92%current scan
Complexity96/100Measured from code scale and structural signals
Maintainability46/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.

52-week repository activity

67 commits across the public default-branch history.

Commit activity provides delivery context. It does not assign a historical RepoWorth to unscanned commits or treat commit count as value.

Jul 27, 2025Weekly commitsJul 19, 2026

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
#1devongovett@devongovett80091.1%Current GitHub contributor snapshot
#2yisibl@yisibl232.6%Current GitHub contributor snapshot
#3kdy1@kdy1141.6%Current GitHub contributor snapshot
#4mischnic@mischnic111.3%Current GitHub contributor snapshot
#5Cason Kervis@cscnk5260.7%Current GitHub contributor snapshot
#6RobinMalfait@RobinMalfait60.7%Current GitHub contributor snapshot
#7chinedufn@chinedufn60.7%Current GitHub contributor snapshot
#8@sapphi-red50.6%Current GitHub contributor snapshot
#9lucacasonato@lucacasonato40.5%Current GitHub contributor snapshot
#10nicksrandall@nicksrandall30.3%Current GitHub contributor snapshot
About lightningcss

What the public repository appears to contain.

An extremely fast CSS parser, transformer, bundler, and minifier written in Rust.

build-toolcompilercssminifierparserrust
License
MPL-2.0
Default branch
master
GitHub stars
7,626
Forks
286
Last public push
Jul 20, 2026
Repository state
Active public repository
Detected language profile3.1MB authored source
Rust94.97%
JavaScript2.3%
HTML1.67%
TypeScript0.55%
CSS0.31%
C/C++0.1%
C0.1%
Source files171
Test files12
Manifests9
Dependencies293
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 signal46/100

Developing based on deterministic repository structure and complexity signals.

Production source799.4K tokens

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

Test evidence10.2K tokens

12 detected test files contribute separately from production code.

Configuration and infrastructure3.2K tokens

9 manifests and 0 workspace boundaries were detected.

Documentation16.8K tokens

8 documentation files remain visible as a distinct enablement signal.

Integration surface228 signals

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

Repository structure3 levels deep

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

Excluded from authored evidence0 files

6 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 evidence672.2KProduction, tests, configuration, and documentation
Estimated implementation output672.2KImplementation, retries, integration, and verification
Engineering oversight53.8 hoursOrientation, integration, tests, and review
Active build time6.7 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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