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

markdown-diff Codebase Valuation

结构感知的 Markdown 差异分析工具 — 基于语义树比对,支持移动/重命名/重排序检测,行级+词级+字符级 inline diff

View zennnnnnn11/markdown-diff on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/zennnnnnn11

markdown-diff

结构感知的 Markdown 差异分析工具 — 基于语义树比对,支持移动/重命名/重排序检测,行级+词级+字符级 inline diff

RepoWorth$3,829Current measured development value · 2.4 active build days
Rebuild complexity80.886/100Profile: Complex
290K code tokens160 source filesTypeScript primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/markdown-diff
Authored code290K tokens · 34,542 source lines
Complexity80.886/100 · Complex
Primary stackTypeScript
Scan coverage94.59% · 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
$3,829

Modeled range $3,063 to $4,595

2.4 active build days18.9 engineering hours236.8K implementation tokens
Repository evidenceMeasured at the scanned commit
290K tokens

34,542 source lines across 160 authored files

77 test files73 dependencies94.59% 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$3,829
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage95%current scan
Complexity81/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.

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
#1zennnnnnn11@zennnnnnn111100.0%Current GitHub contributor snapshot
About markdown-diff

What the public repository appears to contain.

结构感知的 Markdown 差异分析工具 — 基于语义树比对,支持移动/重命名/重排序检测,行级+词级+字符级 inline diff

License
MIT
Default branch
master
GitHub stars
1
Forks
0
Last public push
May 29, 2026
Repository state
Active public repository
Detected language profile1.1MB authored source
TypeScript89.86%
Vue7.89%
CSS1.13%
Rust0.96%
HTML0.11%
Shell0.06%
Source files160
Test files77
Manifests3
Dependencies73
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

Strong based on deterministic repository structure and complexity signals.

Production source107K tokens

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

Test evidence183K tokens

77 detected test files contribute separately from production code.

Configuration and infrastructure3K tokens

3 manifests and 0 workspace boundaries were detected.

Documentation36.4K tokens

11 documentation files remain visible as a distinct enablement signal.

Integration surface1,025 signals

73 dependency declarations and 340 public-interface signals were measured.

Repository structure5 levels deep

0 large files and 5,193 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.

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 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 evidence236.8KProduction, tests, configuration, and documentation
Estimated implementation output236.8KImplementation, retries, integration, and verification
Engineering oversight18.9 hoursOrientation, integration, tests, and review
Active build time2.4 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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