Public record
Software health reportschema 0.31.0 · metrics 2.5.0 · 2026-08-05 23:12 UTC

mavlink / rust-mavlink

MAVLink implementation written in Rust

RustApache-2.0★ 284 stars⑂ 109 forkssince Feb 2016View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

mavlink/rust-mavlink holds a health index of 90 out of 100, placing it in the Excellent band. It scores highest on Vitality (94/100) and lowest on AI Readiness (54/100). It was last updated today. 3 contributors account for most of its recent work.

90
overall / 100
Excellent

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

90
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 76 is calibrated to 90 on the published index scale (record calibration 2026-08-02).

Ownership

828 followers40 public repossince Aug 2011

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iomavlink0.18.052,451470 days ago
crates.iomavlink-core0.18.052,4901188 days agoembeddedmavlinkparserprotocolparsingaerospace
crates.iomavlink-bindgen0.18.052,1241188 days agocligeneratormavlinkparserxmlparsingembeddedaerospace

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

94Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
31.8/36Commit cadence — 46/52 weeks with commits
18/18Commit volume — 141 commits in the last year
10/10OpenSSF Scorecard: Maintained — 29 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year141
human_commit_share0.8
days_since_last_push0
active_weeks_last_year46
How it's scored
27/27Ships releases — 22 releases published
36/36Release recency — latest release 0 days ago
19.8/27Release cadence — a release every ~48.9 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count22
latest_release_tag0.10.13
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases48.9
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

65Good · 17% of overall
How it's scored
39.8/60Stars — 284 stars
16.9/25Forks — 109 forks
7.8/15Watchers — 26 watchers
Inputs used
forks109
stars284
watchers26
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
69.3/80Monthly downloads — 157,065 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesmavlink, mavlink-core, mavlink-bindgen
dependents
ecosystemscrates
total_downloads942,834
monthly_downloads157,065
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

81Excellent · 23% of overall
How it's scored
36/54Bus factor — 3 contributor(s) cover half of all commits
15.5/22.5Commit distribution — top contributor authored 31% of commits
13.5/13.5Contributor breadth — 44 contributors
10/10OpenSSF Scorecard: Contributors — project has 30 contributing companies or organizations
Inputs used
bus_factor3
contributors_sampled44
top_contributor_share0.313
How it's scored
37.4/42Issue resolution — 89% of issues closed
23.7/30PR acceptance — 308/390 decided PRs merged
7.8/13Newcomer PR acceptance — 3/5 first-time contributors' PRs merged in 30d
10.5/15OpenSSF Scorecard: Code-Review — Found 17/22 approved changesets -- score normalized to 7
Inputs used
merged_prs308
open_issues14
closed_issues115
prs_merged_7d1
prs_decided_7d1
prs_merged_30d4
prs_decided_30d6
issue_closed_ratio0.891
closed_unmerged_prs82
first_time_authors_30d3
first_time_prs_merged_30d3
first_time_prs_decided_30d5
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
21/25Owner reach — 828 followers of mavlink
23.7/25Track record — 40 public repos, account ~15 yr old
Inputs used
followers828
owner_typeOrganization
is_verified
owner_loginmavlink
public_repos40
account_age_days5,479

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 3 package(s) on crates
35/35Publish recency — latest publish 0 days ago
20/20Version history — 47 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesmavlink, mavlink-core, mavlink-bindgen
ecosystemscrates
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

71Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 25 out of 25 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://mavlink.github.io/rust-mavlink/mavlink/
10/10Repository description
10/10Topics — 3 topics
10/10Wiki
Inputs used
topicshacktoberfest, mavlink, rust
has_wikiyes
homepagehttps://mavlink.github.io/rust-mavlink/mavlink/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

68Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 25 out of 25 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
5.2/7.5Code-Review — Found 17/22 approved changesets -- score normalized to 7
2.5/2.5Contributors — project has 30 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 29 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
5/5Packaging — packaging workflow detected
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate6
Excluded from scoring (no data or not applicable): signed_releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages2
unassessed_packages40
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 2 resolved dependencies against OSV. 40 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

54Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 60 of 80 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.75
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrap — Cargo.toml, mavlink-bindgen/Cargo.toml, mavlink-core/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 13 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, mavlink-bindgen/Cargo.toml, mavlink-core/Cargo.toml, mavlink/Cargo.toml, mavlink/examples/embedded-async-read/Cargo.toml, mavlink/examples/embedded/Cargo.toml, mavlink/examples/mavlink-dump/Cargo.toml
dependency_bot_commit_share0.13
How it's scored
45/45Type-checkable code — Rust (statically typed)
53.3/55Manageable file sizes — 2/65 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes97,894
source_files_sampled65
oversized_source_files2
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)
0/20MCP server
40/40Runnable examples — examples
Inputs used
example_dirsexamples
has_mcp_signalno
api_schema_files

Key facts

284GitHub stars
44contributors
141commits, last 12 months
0days since last push
22releases
3bus factor
14open issues
crates.iopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 109 ⇿
0Stars
109Forks
21Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

02040608010012010432016-112021-092026-08
Major 0Minor 7Patch 14

Each point covers 9 days.

OpenSSF Scorecard 6.0 / 10
6.0aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-08-05 23:11 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
10CI-Tests25 out of 25 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
7Code-ReviewFound 17/22 approved changesets -- score normalized to 7
10Contributorsproject has 30 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained29 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 36
RegistryPackageVersion constraintManifest
crates.ioanstyle1.0.11mavlink-bindgen/Cargo.toml
crates.ioanstyle-parse1.0.0mavlink-bindgen/Cargo.toml
crates.ioanstyle-query1.1.4mavlink-bindgen/Cargo.toml
crates.ioclap~4.6.0mavlink-bindgen/Cargo.toml
crates.ioclap_builder4.3.24mavlink-bindgen/Cargo.toml
crates.ioclap_lex1.0.0mavlink-bindgen/Cargo.toml
crates.iocrc-anymavlink-bindgen/Cargo.toml
crates.ioproc-macro21.0.43mavlink-bindgen/Cargo.toml
crates.ioquick-xml0.41mavlink-bindgen/Cargo.toml
crates.ioquote1mavlink-bindgen/Cargo.toml
crates.ioregex1.0mavlink-bindgen/Cargo.toml
crates.ioserde1.0.115mavlink-bindgen/Cargo.toml
crates.iothiserror2.0.12mavlink-bindgen/Cargo.toml
crates.ioarbitrary1.4mavlink-core/Cargo.toml
crates.ioasync-trait0.1.18mavlink-core/Cargo.toml
crates.iobyteordermavlink-core/Cargo.toml
crates.iocrc-anymavlink-core/Cargo.toml
crates.ioembedded-io0.7mavlink-core/Cargo.toml
crates.ioembedded-io-async0.7mavlink-core/Cargo.toml
crates.iofutures0.3mavlink-core/Cargo.toml
crates.iorand0.10.1mavlink-core/Cargo.toml
crates.ioserde1.0.115mavlink-core/Cargo.toml
crates.ioserde_arrays0.2.0mavlink-core/Cargo.toml
crates.ioserialport4.7.2mavlink-core/Cargo.toml
crates.iosha20.11mavlink-core/Cargo.toml
crates.iotokio1.0mavlink-core/Cargo.toml
crates.iotokio-serial5.5mavlink-core/Cargo.toml
crates.iomavlink-core=0.18.0mavlink/Cargo.toml
crates.ionum-traitsmavlink/Cargo.toml
crates.ionum-derivemavlink/Cargo.toml
crates.iobitflagsmavlink/Cargo.toml
crates.ioserde1.0.115mavlink/Cargo.toml
crates.ioserde_arrays0.2.0mavlink/Cargo.toml
crates.ioarbitrary1.4mavlink/Cargo.toml
crates.iorand0.10.1mavlink/Cargo.toml
crates.iots-rs11.0.1mavlink/Cargo.toml
All dependencies 42

Full resolved dependency set from the GitHub dependency graph: 25 direct and 17 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
crates.ioanstyledirect
crates.ioanstyle-parsedirect
crates.ioanstyle-querydirect
crates.ioarbitrarydirect
crates.ioasync-traitdirect
crates.ioclapdirect
crates.ioclap_builderdirect
crates.ioclap_lexdirect
crates.ioembedded-iodirect
crates.ioembedded-io-asyncdirect
crates.iofuturesdirect
crates.iomavlink-core0.18.0direct
crates.ioproc-macro2direct
crates.ioquick-xmldirect
crates.ioquotedirect
crates.ioranddirect
crates.ioregexdirect
crates.ioserdedirect
crates.ioserde_arraysdirect
crates.ioserialportdirect
crates.iosha2direct
crates.iothiserrordirect
crates.iotokiodirect
crates.iotokio-serialdirect
crates.iots-rsdirect
crates.iocortex-mindirect
crates.iocortex-m-rtindirect
crates.ioembassy-executorindirect
crates.ioembassy-stm32indirect
crates.ioembassy-timeindirect
crates.ioembedded-halindirect
crates.ioinstaindirect
crates.iomavlink-bindgen0.18.0indirect
crates.ionbindirect
crates.iopanic-haltindirect
crates.iopanic-rtt-targetindirect
crates.iortt-targetindirect
crates.ioserde_jsonindirect
crates.ioserde_testindirect
crates.iostatic_cellindirect
crates.iostm32f3xx-halindirect
crates.iotempfileindirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 2 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 40 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

No known advisories affect the assessed dependencies.

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.5.0, schema v0.31.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.