Current repository readingScanned Jul 24, 2026, 4:12 PM UTC

iD Codebase Valuation

๐Ÿ†” The easy-to-use OpenStreetMap editor in JavaScript.

View openstreetmap/iD on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/openstreetmap

iD

๐Ÿ†” The easy-to-use OpenStreetMap editor in JavaScript.

RepoWorth$14,409Current measured development value ยท 8.8 active build days
Rebuild complexity82.167/100Profile: Complex
1.1M code tokens539 source filesJavaScript primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/id
Authored code1.1M tokens ยท 125,273 source lines
Complexity82.167/100 ยท Complex
Primary stackJavaScript
Scan coverage99.43% ยท 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
$14,409

Modeled range $11,527 to $17,291

8.8 active build days70.8 engineering hours885K implementation tokens
Repository evidenceMeasured at the scanned commit
1.1M tokens

125,273 source lines across 539 authored files

142 test files78 dependencies99.43% 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$14,409
Current measured reading
Measured ยท Jul 24, 2026Data through ยท Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage99%current scan
Complexity82/100Measured from code scale and structural signals
Maintainability75/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

1,020 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
#1bhousel@bhousel4,51132.9%Current GitHub contributor snapshot
#2quincylvania@quincylvania3,01322.0%Current GitHub contributor snapshot
#3jfirebaugh@jfirebaugh1,88213.7%Current GitHub contributor snapshot
#4tyrasd@tyrasd1,3359.7%Current GitHub contributor snapshot
#5tmcw@tmcw1,2749.3%Current GitHub contributor snapshot
#6ansis@ansis7015.1%Current GitHub contributor snapshot
#7samanpwbb@samanpwbb5053.7%Current GitHub contributor snapshot
#8k-yle@k-yle1981.4%Current GitHub contributor snapshot
#9kymckay@kymckay1611.2%Current GitHub contributor snapshot
#10kepta@kepta1311.0%Current GitHub contributor snapshot
About iD

What the public repository appears to contain.

๐Ÿ†” The easy-to-use OpenStreetMap editor in JavaScript.

d3editormappingopenstreetmap
License
ISC
Default branch
develop
GitHub stars
3,841
Forks
1,463
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile4.4MB authored source
JavaScript83.58%
TypeScript10.34%
CSS6.01%
HTML0.06%
Source files539
Test files142
Manifests1
Dependencies78
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 signal75/100

Established based on deterministic repository structure and complexity signals.

Production source702.3K tokens

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

Test evidence389.5K tokens

142 detected test files contribute separately from production code.

Configuration and infrastructure3.7K tokens

1 manifests and 0 workspace boundaries were detected.

Documentation145.9K tokens

13 documentation files remain visible as a distinct enablement signal.

Integration surface4,931 signals

78 dependency declarations and 563 public-interface signals were measured.

Repository structure4 levels deep

0 large files and 13,076 branch signals add structural context.

Excluded from authored evidence0 files

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

architecture

Interface builder

At least 500 deterministic public interface signals were measured in source.

enablement

Documented foundation

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

architecture

Integration surface

At least 1,000 deterministic integration signals were measured in source.

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 scaleHigh

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 evidence885KProduction, tests, configuration, and documentation
Estimated implementation output885KImplementation, retries, integration, and verification
Engineering oversight70.8 hoursOrientation, integration, tests, and review
Active build time8.8 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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