Current repository readingScanned Jul 25, 2026, 10:54 AM UTC

luajit2-flame-rs Codebase Valuation

Rust/eBPF LuaJIT CPU flame graph profiler with Lua source-line stack resolution.

View cppcoffee/luajit2-flame-rs on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/cppcoffee

luajit2-flame-rs

Rust/eBPF LuaJIT CPU flame graph profiler with Lua source-line stack resolution.

RepoWorth$8,674Current measured development value · 6.5 active build days
Rebuild complexity50.15/100Profile: Layered
705.1K code tokens14 source filesC primary language
Scanned Jul 25, 2026Public GitHub repositorycodevaluation.com/repoworth/luajit2-flame-rs
Authored code705.1K tokens · 133,319 source lines
Complexity50.15/100 · Layered
Primary stackC
Scan coverage100% · 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
$8,674

Modeled range $6,939 to $10,409

6.5 active build days51.6 engineering hours645K implementation tokens
Repository evidenceMeasured at the scanned commit
705.1K tokens

133,319 source lines across 14 authored files

3 test files25 dependencies100% scan coverage
Repository evidence

Building the historical and contribution view.

The headline RepoWorth and measured source facts are ready. Comparable history, accepted changes, and badge evidence will appear here as enrichment finishes.

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
#1cppcoffee@cppcoffee40100.0%Current GitHub contributor snapshot
About luajit2-flame-rs

What the public repository appears to contain.

Rust/eBPF LuaJIT CPU flame graph profiler with Lua source-line stack resolution.

bpfebpfflamegraphluajitluajit2
License
BSD-2-Clause
Default branch
main
GitHub stars
0
Forks
0
Last public push
Jul 21, 2026
Repository state
Active public repository
Detected language profile3.2MB authored source
C/C++97.59%
Rust1.71%
C0.58%
Lua0.13%
Source files14
Test files3
Manifests1
Dependencies25
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 signal73/100

Established based on deterministic repository structure and complexity signals.

Production source702.7K tokens

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

Test evidence2.4K tokens

3 detected test files contribute separately from production code.

Configuration and infrastructure217 tokens

1 manifests and 0 workspace boundaries were detected.

Documentation2.2K tokens

1 documentation files remain visible as a distinct enablement signal.

Integration surface2 signals

25 dependency declarations and 0 public-interface signals were measured.

Repository structure1 levels deep

0 large files and 327 branch signals add structural context.

Excluded from authored evidence0 files

0 generated files were identified. Ignored and generated material does not inflate RepoWorth.

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.

ComplexityModerate

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

What this valuation includes.

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