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

flight-finder Codebase Valuation

Flight price tracker. Self-hosted, open source, bring your own LLM. The price trail airlines don't show you.

View affromero/flight-finder on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/affromero

flight-finder

Flight price tracker. Self-hosted, open source, bring your own LLM. The price trail airlines don't show you.

RepoWorth$7,283Current measured development value · 4.5 active build days
Rebuild complexity83.119/100Profile: Complex
547.5K code tokens437 source filesTypeScript primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/flight-finder
Authored code547.5K tokens · 63,676 source lines
Complexity83.119/100 · Complex
Primary stackTypeScript
Scan coverage96.07% · 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
$7,283

Modeled range $5,827 to $8,740

4.5 active build days35.6 engineering hours445K implementation tokens
Repository evidenceMeasured at the scanned commit
547.5K tokens

63,676 source lines across 437 authored files

111 test files79 dependencies96.07% 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$7,283
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage96%current scan
Complexity83/100Measured from code scale and structural signals
Maintainability74/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
#1affromero@affromero88396.7%Current GitHub contributor snapshot
#2maxjb-xyz@maxjb-xyz91.0%Current GitHub contributor snapshot
#3ms32035@ms3203580.9%Current GitHub contributor snapshot
#4ssantss@ssantss60.7%Current GitHub contributor snapshot
#5Darth-Ness@Darth-Ness40.4%Current GitHub contributor snapshot
#6gwendolinw@gwendolinw30.3%Current GitHub contributor snapshot
About flight-finder

What the public repository appears to contain.

Flight price tracker. Self-hosted, open source, bring your own LLM. The price trail airlines don't show you.

claudedockerflight-pricesflightsllmnextjsopen-sourceplaywrightprice-trackerself-hostedtypescriptweb-scraping
License
MIT
Default branch
main
GitHub stars
115
Forks
21
Last public push
Jul 23, 2026
Repository state
Active public repository
Detected language profile2.1MB authored source
TypeScript81.79%
Shell8.51%
CSS8.3%
Rust0.74%
JavaScript0.47%
HTML0.19%
Source files437
Test files111
Manifests6
Dependencies79
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 source367.4K tokens

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

Test evidence180.1K tokens

111 detected test files contribute separately from production code.

Configuration and infrastructure2.1K tokens

6 manifests and 0 workspace boundaries were detected.

Documentation35.5K tokens

10 documentation files remain visible as a distinct enablement signal.

Integration surface3,003 signals

79 dependency declarations and 566 public-interface signals were measured.

Repository structure9 levels deep

0 large files and 7,263 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

Interface builder

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

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.

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 evidence445KProduction, tests, configuration, and documentation
Estimated implementation output445KImplementation, retries, integration, and verification
Engineering oversight35.6 hoursOrientation, integration, tests, and review
Active build time4.5 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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