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

MAVSDK Codebase Valuation

API and library for MAVLink compatible systems written in C++ 20

View mavlink/MAVSDK on GitHub
Open share card
CodeValuation.com
RepoWorth
github.com/mavlink

MAVSDK

API and library for MAVLink compatible systems written in C++ 20

RepoWorth$24,538Current measured development value · 14.9 active build days
Rebuild complexity83.976/100Profile: Complex
1.8M code tokens817 source filesC++ primary language
Scanned Jul 24, 2026Public GitHub repositorycodevaluation.com/repoworth/mavsdk
Authored code1.8M tokens · 246,912 source lines
Complexity83.976/100 · Complex
Primary stackC++
Scan coverage95.59% · 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
$24,538

Modeled range $19,630 to $29,445

14.9 active build days119.4 engineering hours1.5M implementation tokens
Repository evidenceMeasured at the scanned commit
1.8M tokens

246,912 source lines across 817 authored files

42 test files5 dependencies95.59% 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$24,538
Current measured reading
Measured · Jul 24, 2026Data through · Jul 24, 2026
Measurement basisCurrent readingCurrent published repository scan
Evidence coverage96%current scan
Complexity84/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.

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
#1julianoes@julianoes4,36673.7%Current GitHub contributor snapshot
#2JonasVautherin@JonasVautherin1,11518.8%Current GitHub contributor snapshot
#3Bartok@Bartok91372.3%Current GitHub contributor snapshot
#4hamishwillee@hamishwillee751.3%Current GitHub contributor snapshot
#5darioxz@darioxz611.0%Current GitHub contributor snapshot
#6douglaswsilva@douglaswsilva500.8%Current GitHub contributor snapshot
#7bansiesta@bansiesta330.6%Current GitHub contributor snapshot
#8irsdkv@irsdkv330.6%Current GitHub contributor snapshot
#9bkueng@bkueng320.5%Current GitHub contributor snapshot
#10ykhedar@ykhedar260.4%Current GitHub contributor snapshot
About MAVSDK

What the public repository appears to contain.

API and library for MAVLink compatible systems written in C++ 20

ardupilotcppcpp17mavlinkpx4
License
BSD-3-Clause
Default branch
main
GitHub stars
914
Forks
632
Last public push
Jul 23, 2026
Repository state
Active public repository
Detected language profile8.1MB authored source
C++72.18%
Python16.96%
C/C++9.43%
Shell0.68%
C0.5%
JavaScript0.14%
CSS0.1%
Vue0.01%
Source files817
Test files42
Manifests1
Dependencies5
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 source1.7M tokens

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

Test evidence95.2K tokens

42 detected test files contribute separately from production code.

Configuration and infrastructure247 tokens

1 manifests and 0 workspace boundaries were detected.

Documentation348.5K tokens

421 documentation files remain visible as a distinct enablement signal.

Integration surface1,240 signals

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

Repository structure8 levels deep

0 large files and 20,306 branch signals add structural context.

Excluded from authored evidence0 files

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

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 evidence1.5MProduction, tests, configuration, and documentation
Estimated implementation output1.5MImplementation, retries, integration, and verification
Engineering oversight119.4 hoursOrientation, integration, tests, and review
Active build time14.9 daysModeled effort represented by the current source state
Evidence boundary

What this valuation includes.

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