Current repository readingScanned Jul 24, 2026, 5:22 AM UTC

napi-rs Codebase Valuation

A framework for building compiled Node.js add-ons in Rust via Node-API

View napi-rs/napi-rs on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/napi-rs

napi-rs

A framework for building compiled Node.js add-ons in Rust via Node-API

RepoWorth$12,710Current measured development value · 7.4 active build days
Rebuild complexity92.623/100Profile: Complex
883.4K code tokens368 source filesRust primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/napi-rs
Authored code883.4K tokens · 117,479 source lines
Complexity92.623/100 · Complex
Primary stackRust
Scan coverage99.79% · 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
$12,710

Modeled range $10,168 to $15,252

7.4 active build days59.1 engineering hours738.7K implementation tokens
Repository evidenceMeasured at the scanned commit
883.4K tokens

117,479 source lines across 368 authored files

90 test files671 dependencies99.79% 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$12,710
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage100%current scan
Complexity93/100Measured from code scale and structural signals
Maintainability57/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

472 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
#1LongYinan@Brooooooklyn28259.5%Current GitHub contributor snapshot
#2forehalo@forehalo469.7%Current GitHub contributor snapshot
#3richerfu@richerfu357.4%Current GitHub contributor snapshot
#4@sapphi-red214.4%Current GitHub contributor snapshot
#5messense@messense214.4%Current GitHub contributor snapshot
#6trivikr@trivikr204.2%Current GitHub contributor snapshot
#7h-a-n-a@h-a-n-a173.6%Current GitHub contributor snapshot
#8SyMind@SyMind153.2%Current GitHub contributor snapshot
#9oyyd@oyyd91.9%Current GitHub contributor snapshot
#10skirsdeda@skirsdeda81.7%Current GitHub contributor snapshot
About napi-rs

What the public repository appears to contain.

A framework for building compiled Node.js add-ons in Rust via Node-API

javascriptnapinapi-rsnodenode-apinodejsrust
License
NOASSERTION
Default branch
main
GitHub stars
7,845
Forks
399
Last public push
Jul 23, 2026
Repository state
Active public repository
Detected language profile3.7MB authored source
Rust72.09%
TypeScript23.25%
JavaScript4.64%
HTML0.03%
Source files368
Test files90
Manifests31
Dependencies671
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 signal57/100

Developing based on deterministic repository structure and complexity signals.

Production source796.4K tokens

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

Test evidence87K tokens

90 detected test files contribute separately from production code.

Configuration and infrastructure9.5K tokens

31 manifests and 0 workspace boundaries were detected.

Documentation57.6K tokens

22 documentation files remain visible as a distinct enablement signal.

Integration surface1,105 signals

671 dependency declarations and 989 public-interface signals were measured.

Repository structure8 levels deep

0 large files and 11,800 branch signals add structural context.

Excluded from authored evidence0 files

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

architecture

Dependency ecosystem

At least 500 dependency declarations were measured across supported manifests.

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.

VerificationModerate

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 evidence738.7KProduction, tests, configuration, and documentation
Estimated implementation output738.7KImplementation, retries, integration, and verification
Engineering oversight59.1 hoursOrientation, integration, tests, and review
Active build time7.4 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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