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

furnace Codebase Valuation

a multi-system chiptune tracker compatible with DefleMask modules

View tildearrow/furnace on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/tildearrow

furnace

a multi-system chiptune tracker compatible with DefleMask modules

RepoWorth$359,021Current measured development value · 204.0 active build days
Rebuild complexity97.097/100Profile: Complex
26.8M code tokens6.1K source filesC++ primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/furnace
Authored code26.8M tokens · 2,126,172 source lines
Complexity97.097/100 · Complex
Primary stackC++
Scan coverage99.99% · 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
$359,021

Modeled range $287,217 to $430,825

204.0 active build days1631.8 engineering hours20.4M implementation tokens
Repository evidenceMeasured at the scanned commit
26.8M tokens

2,126,172 source lines across 6,078 authored files

169 test files102 dependencies99.99% 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$359,021
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity97/100Measured from code scale and structural signals
Maintainability43/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,180 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
#1tildearrow@tildearrow8,26278.9%Current GitHub contributor snapshot
#2cam900@cam9007997.6%Current GitHub contributor snapshot
#3Eknous-P@Eknous-P3633.5%Current GitHub contributor snapshot
#4ElectricKeet@ElectricKeet3313.2%Current GitHub contributor snapshot
#5freq-mod@freq-mod1851.8%Current GitHub contributor snapshot
#6LTVA1@LTVA11651.6%Current GitHub contributor snapshot
#7akumanatt@akumanatt1431.4%Current GitHub contributor snapshot
#8yohannd1@yohannd1970.9%Current GitHub contributor snapshot
#9djtuBIG-MaliceX@djtuBIG-MaliceX720.7%Current GitHub contributor snapshot
#10Kagamiin@Kagamiin490.5%Current GitHub contributor snapshot
About furnace

What the public repository appears to contain.

a multi-system chiptune tracker compatible with DefleMask modules

chiptuneemulatormusictracker-music
License
NOASSERTION
Default branch
master
GitHub stars
3,740
Forks
313
Last public push
Jul 24, 2026
Repository state
Active public repository
Detected language profile85.4MB authored source
C++55.89%
C25.31%
C/C++10.9%
HTML5.75%
JavaScript1.06%
Shell0.44%
Python0.23%
Java0.17%
Source files6,078
Test files169
Manifests2
Dependencies102
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 signal43/100

Developing based on deterministic repository structure and complexity signals.

Production source26.3M tokens

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

Test evidence528.9K tokens

169 detected test files contribute separately from production code.

Configuration and infrastructure0 tokens

2 manifests and 0 workspace boundaries were detected.

Documentation670.6K tokens

471 documentation files remain visible as a distinct enablement signal.

Integration surface3,506 signals

102 dependency declarations and 369 public-interface signals were measured.

Repository structure8 levels deep

0 large files and 209,757 branch signals add structural context.

Excluded from authored evidence0 files

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

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.

scale

System-scale codebase

More than 10 million measured source tokens in one qualifying snapshot.

complexity

Branching engine

At least 100,000 deterministic control-flow and branch signals were measured in source.

breadth

Polyglot system

At least five languages each represent one percent or more of measured source tokens.

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 evidence20.4MProduction, tests, configuration, and documentation
Estimated implementation output20.4MImplementation, retries, integration, and verification
Engineering oversight1631.8 hoursOrientation, integration, tests, and review
Active build time204.0 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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