Current repository readingScanned Jul 24, 2026, 5:53 AM UTC
mmntjs Codebase Valuation
Most teams don't keep using moment.js because they love it. They keep using it because rewriting date logic across a large codebase is risky, expensive, and never becomes this quarter's priority. mmntjs designed for that reality. Drop-in replacement for moment.js
Most teams don't keep using moment.js because they love it. They keep using it because rewriting date logic across a large codebase is risky, expensive, and never becomes this quarter's priority. mmntjs designed for that reality. Drop-in replacement for moment.js
RepoWorth$19,820Current measured development value · 12.3 active build days
Rebuild complexity80.851/100Profile: Complex
1.5M code tokens659 source filesTypeScript primary language
Authored code1.5M tokens · 163,547 source lines
Complexity80.851/100 · Complex
Primary stackTypeScript
Scan coverage90.25% · 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$19,820
Modeled range $15,856 to $23,784
12.3 active build days98.1 engineering hours1.2M implementation tokens
Repository evidenceMeasured at the scanned commit1.5M tokens
163,547 source lines across 659 authored files
320 test files31 dependencies90.25% 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$19,820
Current measured reading
Measurement basisCurrent readingCurrent published repository scanEvidence coverage90%current scanComplexity81/100Measured from code scale and structural signalsMaintainability74/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.
Most teams don't keep using moment.js because they love it. They keep using it because rewriting date logic across a large codebase is risky, expensive, and never becomes this quarter's priority. mmntjs designed for that reality. Drop-in replacement for moment.js
datelibrarymomentmoment-jsmomentjsperformancetime
License
Not detected
Default branch
main
GitHub stars
0
Forks
0
Last public push
May 26, 2026
Repository state
Active public repository
Detected language profile5.2MB authored source
TypeScript86.35%
JavaScript12.93%
CSS0.4%
Shell0.32%
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 signal74/100
Established based on deterministic repository structure and complexity signals.
Production source414.6K tokens
First-party implementation tokens eligible for the modeled code-scale input.
Test evidence1.1M tokens
320 detected test files contribute separately from production code.
Configuration and infrastructure4.6K tokens
2 manifests and 0 workspace boundaries were detected.
Documentation186.3K tokens
33 documentation files remain visible as a distinct enablement signal.
Integration surface4,050 signals
31 dependency declarations and 762 public-interface signals were measured.
Repository structure4 levels deep
0 large files and 14,880 branch signals add structural context.
Excluded from authored evidence0 files
6 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 evidence1.2MProduction, tests, configuration, and documentation
Estimated implementation output1.2MImplementation, retries, integration, and verification
Engineering oversight98.1 hoursOrientation, integration, tests, and review
Active build time12.3 daysModeled effort represented by the current source state
Evidence boundary
What this valuation includes.
CodeValuation.com counted supported authored source on commit 263f0884cab067e2c34f38b299cefd60582e459e, measured deterministic repository signals, then estimated implementation, rework, testing, integration, and engineering oversight.
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.
