Repo brief: PX4/PX4-Autopilot

Generated by RepoPilot · document generated 2026-09-16 · concise human review Evidence snapshot · analyzed 2026-09-16T01:49:19.404Z · commit cbc6a6f7abbd

Verdict

Healthy — Strong maintenance signals

• Last commit today
• 28+ active contributors
• Distributed ownership (top contributor 30% of recent commits)
• BSD-3-Clause licensed
• 2 more receipts on the live page

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests, cross-checked against OpenSSF Scorecard

What it is

PX4 Autopilot is an open-source flight control stack for autonomous drones, multirotors, fixed-wing aircraft, VTOL, and rovers. Built on uORB (a DDS-compatible publish/subscribe middleware), it provides real-time flight dynamics, sensor fusion, navigation, and actuator control across 40+ supported autopilot hardware boards and diverse sensor/radio ecosystems. Monorepo organized by abstraction layers: src/drivers/ contains hardware-specific modules (e.g., vertiq_io, voxl_esc, adc) with standardized CMakeLists.txt and Kconfig; src/modules/ houses flight logic; uORB middleware handles inter-module communication. Each driver is self-contained with its own YAML configuration and parameter…

Start here

Open these first:

• src/drivers/Kconfig — Root configuration file for all driver subsystems; determines which hardware drivers are compiled into the autopilot.
• src/drivers/actuators/vertiq_io/vertiq_io.cpp — Primary entry point for Vertiq motor driver integration; handles initialization and command dispatch to motor control…
• src/drivers/actuators/voxl_esc/voxl_esc.cpp — VOXL ESC driver implementation; manages electronic speed controller communication and telemetry collection.
• src/drivers/barometer/bmp280/BMP280.cpp — Reference barometer driver implementation showing standard sensor initialization and data reading patterns used across PX4.
• src/drivers/adc/board_adc/ADC.cpp — Board-level ADC driver providing unified interface for analog-to-digital conversion across different hardware platforms.

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Repository provides no package.json or setup.py in top-level (CMake is primary build system). Clone with: git clone https://github.com/PX4/PX4-Autopilot.git && cd PX4-Autopilot. Then consult repository's CMake-based bui…

Daily commands:

Build system is CMake-based; no conventional npm/pip install. Requires platform-specific toolchain (NuttX cross-compiler for flight controllers, or native build for SITL simulation). Start with: mkdir build && cd build…

…shortened for this brief.

Key cautions & unknowns

• Scorecard: default branch unprotected (0/10)
• CMake cross-compilation requires hardware-specific toolchains (arm-none-eabi for NuttX boards) not auto-installed; mismatch causes cryptic linker errors. uORB messages (generated from definitions not in file list) must…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests
• OpenSSF Scorecard

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.