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

maturin Codebase Valuation

Build and publish crates with pyo3, cffi and uniffi bindings as well as rust binaries as python packages

View PyO3/maturin on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/PyO3

maturin

Build and publish crates with pyo3, cffi and uniffi bindings as well as rust binaries as python packages

RepoWorth$4,535Current measured development value · 2.7 active build days
Rebuild complexity91.083/100Profile: Complex
325K code tokens225 source filesRust primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/maturin
Authored code325K tokens · 38,888 source lines
Complexity91.083/100 · Complex
Primary stackRust
Scan coverage92.31% · 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
$4,535

Modeled range $3,628 to $5,443

2.7 active build days21.3 engineering hours265.7K implementation tokens
Repository evidenceMeasured at the scanned commit
325K tokens

38,888 source lines across 225 authored files

25 test files1,398 dependencies92.31% 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$4,535
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage92%current scan
Complexity91/100Measured from code scale and structural signals
Maintainability60/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
#1messense@messense2,34071.6%Current GitHub contributor snapshot
#2konstin@konstin74722.9%Current GitHub contributor snapshot
#3dependabot-support@dependabot-support441.3%Current GitHub contributor snapshot
#4davidhewitt@davidhewitt341.0%Current GitHub contributor snapshot
#5ijl@ijl230.7%Current GitHub contributor snapshot
#6e-nomem@e-nomem210.6%Current GitHub contributor snapshot
#7ravenexp@ravenexp190.6%Current GitHub contributor snapshot
#8mbrobbel@mbrobbel160.5%Current GitHub contributor snapshot
#9mbway@mbway150.5%Current GitHub contributor snapshot
#10Tpt@Tpt100.3%Current GitHub contributor snapshot
About maturin

What the public repository appears to contain.

Build and publish crates with pyo3, cffi and uniffi bindings as well as rust binaries as python packages

cfficpythoncross-compilehacktoberfestmanylinuxpackagingpyo3pypipypypythonuniffiwheels
License
Apache-2.0
Default branch
main
GitHub stars
5,715
Forks
422
Last public push
Jul 23, 2026
Repository state
Active public repository
Detected language profile1.4MB authored source
Rust96.36%
Python2.95%
JavaScript0.38%
Shell0.29%
CSS0.02%
Source files225
Test files25
Manifests119
Dependencies1,398
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 signal60/100

Established based on deterministic repository structure and complexity signals.

Production source287.8K tokens

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

Test evidence37.2K tokens

25 detected test files contribute separately from production code.

Configuration and infrastructure10K tokens

119 manifests and 0 workspace boundaries were detected.

Documentation265.8K tokens

104 documentation files remain visible as a distinct enablement signal.

Integration surface227 signals

1,398 dependency declarations and 0 public-interface signals were measured.

Repository structure6 levels deep

0 large files and 5,007 branch signals add structural context.

Excluded from authored evidence0 files

13 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

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 scaleModerate

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 evidence265.7KProduction, tests, configuration, and documentation
Estimated implementation output265.7KImplementation, retries, integration, and verification
Engineering oversight21.3 hoursOrientation, integration, tests, and review
Active build time2.7 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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