Current repository readingScanned Jul 24, 2026, 6:59 PM UTC

eslint-plugin-qunit Codebase Valuation

ESLint plugin containing rules useful for QUnit tests.

View qunitjs/eslint-plugin-qunit on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/qunitjs

eslint-plugin-qunit

ESLint plugin containing rules useful for QUnit tests.

RepoWorth$1,438Current measured development value · Less than one active build day
Rebuild complexity68.59/100Profile: Complex
115.6K code tokens85 source filesJavaScript primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/eslint-plugin-qunit
Authored code115.6K tokens · 14,450 source lines
Complexity68.59/100 · Complex
Primary stackJavaScript
Scan coverage98.23% · 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,438

Modeled range $1,150 to $1,726

1.0 active build days7.6 engineering hours95.4K implementation tokens
Repository evidenceMeasured at the scanned commit
115.6K tokens

14,450 source lines across 85 authored files

41 test files33 dependencies98.23% 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,438
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage98%current scan
Complexity69/100Measured from code scale and structural signals
Maintainability79/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

38 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
#1platinumazure@platinumazure27163.0%Current GitHub contributor snapshot
#2bmish@bmish14032.6%Current GitHub contributor snapshot
#3edg2s@edg2s51.2%Current GitHub contributor snapshot
#4mitchlloyd@mitchlloyd30.7%Current GitHub contributor snapshot
#5Krinkle@Krinkle30.7%Current GitHub contributor snapshot
#6ddzz@ddzz20.5%Current GitHub contributor snapshot
#7raycohen@raycohen20.5%Current GitHub contributor snapshot
#8ventuno@ventuno20.5%Current GitHub contributor snapshot
#9LucasHill@LucasHill10.2%Current GitHub contributor snapshot
#10dwickern@dwickern10.2%Current GitHub contributor snapshot
About eslint-plugin-qunit

What the public repository appears to contain.

ESLint plugin containing rules useful for QUnit tests.

eslint-pluginqunit
License
MIT
Default branch
main
GitHub stars
33
Forks
25
Last public push
Jul 13, 2026
Repository state
Active public repository
Detected language profile490.7KB authored source
JavaScript100%
Source files85
Test files41
Manifests1
Dependencies33
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 signal79/100

Strong based on deterministic repository structure and complexity signals.

Production source43.8K tokens

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

Test evidence71.8K tokens

41 detected test files contribute separately from production code.

Configuration and infrastructure3.1K tokens

1 manifests and 0 workspace boundaries were detected.

Documentation10K tokens

2 documentation files remain visible as a distinct enablement signal.

Integration surface212 signals

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

Repository structure3 levels deep

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

Excluded from authored evidence0 files

40 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 evidence95.4KProduction, tests, configuration, and documentation
Estimated implementation output95.4KImplementation, retries, integration, and verification
Engineering oversight7.6 hoursOrientation, integration, tests, and review
Active build time1.0 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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