logo

mavlink/mavsdk

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

Hosted by Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

mavlink/mavsdk has 950+ stars and 600+ forks on GitHub, is written in C++, and was last pushed on Oct 19, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 56 minutes ago
Type:Library / SDKCategory(s):Robotics & Autonomous SystemsEmbedded & IoTSystems, Hardware & HPC
Added to GitGenius on October 15th, 2026
Created on June 19th, 2017
Open Issues & Pull Requests: 39 (-2)
GitHub issues: Enabled
Number of forks: 648
Total Stargazers: 952 (+0)
Total Subscribers: 47 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.9 hours
Mean response time: 75.2 days
90th percentile: 10.9 days
Tracked items: 226

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

1 person did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 3% of issues opened in the past year have never received a reply. Work labelled "bug" is answered fastest, typically in about 8 hours, while "enhancement" waits about 5 days. 88% of issues opened in the past year have been closed, leaving a working backlog. Three people close 86% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 13
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 701 days
Stale 30+ days: 9
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (37)
  • question (35)
  • feature (30)
  • enhancement (23)
  • more_info_needed (16)
  • help wanted (3)
  • v3 (3)
  • docs (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

MAVSDK is a library providing a high-level API to MAVLink-compatible systems written in C++.

MAVSDK solves the problem of communicating with MAVLink-compatible drones and robotics systems by abstracting away the complexity of the MAVLink protocol. It offers both synchronous blocking API calls and asynchronous callbacks, allowing developers to choose the interaction model that suits their use case. The library is designed to be lightweight and fast while maintaining full compliance with MAVLink standards. The API is defined through protocol buffer IDL files, which enables the generation of idiomatic bindings for multiple programming languages, each using the conventions and tooling its users expect.

Developers should choose MAVSDK if they are building applications for drones or MAVLink-compatible systems and want a simpler alternative to working directly with the protocol. The tool suits projects targeting Linux, macOS, Windows, iOS, and Android. Language bindings are available for C, Python, and Kotlin, with Python installable directly from PyPI. Bindings can connect either directly to the C++ library through a C wrapper with no extra process overhead, or over gRPC through a separate mavsdk_server process for clients in external repositories. The library is extensible through the MavlinkDirect plugin for custom functionality.

Development activity shows consistent engagement with the codebase through regular updates to core communication libraries and plugin implementations. The project maintains active documentation and provides migration guidance for users upgrading between major versions. Releases bundle the C++ library together with all language bindings, ensuring consistency across platforms and languages.