The official build framework for the Armbian Linux distribution. This repository contains the complete toolchain and scripts required to compile custom OS images from source, including kernel configuration, U-Boot handling, and board-specific tweaks for various ARM and ARM64 single-board computers.
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 78%
Response Time: -
First Timer Success: 76%
armbian/build has a recorded first-timer success rate of 75.6%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in armbian/build respond to incoming external pull requests in approximately 0.0 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 69.4 places armbian/build in the A tier.
The external contributor pull request merge rate for armbian/build is 78.4%, based on public PR activity from non-core contributors.
armbian/build currently has 13 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
The official build framework for the Armbian Linux distribution. This repository contains the complete toolchain and scripts required to compile custom OS images from source, including kernel configuration, U-Boot handling, and board-specific tweaks for various ARM and ARM64 single-board computers.
Highly welcoming maintainers in armbian/build. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/armbian/build?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 03:00 to 07:00 UTC (03:00 - 07:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~25 hours (96% approval). Large PRs (>500 lines) take ~187 hours (35% approval). Keep your diff compact for rapid review.
What happened? Board: FriendlyElec CM3588 NAS (RK3588), Armbian community image, kernel 6.18.44-current-rockchip64 (prebuilt image, not built locally). patch/kernel/archive/rockchip64-6.18/rk35xx-montjoie-crypto-v2-rk35xx.patch (also in 6.12 and 7.3) registers every rk_crypto2 algorithm with cra_priority = 300, the same priority as the ARMv8 Crypto Extensions drivers (xts-aes-ce, sha256-lib). Being registered later, the rk_crypto2 engine wins: with the module loaded at boot (CONFIG_CRYPTO_DEV_ROCKCHIP2=m, node crypto@fe370000 enabled), /proc/crypto lists xts-aes-rk2 first for xts(aes), and every new dm-crypt mapping uses it. The engine serves one request at a time, each with a DMA round trip, so it is much slower than the cores: dm-crypt, aes-xts-plain64, NVMe rk_crypto2 cores (xts-aes-ce) 1 GiB direct read through dm-crypt 125 MB/s 588 MB/s LUKS + Btrfs, write 60 MB/s 187 MB/s LUKS + Btrfs, read 111 MB/s 425 MB/s SHA-256 through AF_ALG, 4 KiB requests 1 process 8 proc
Which feature would you like to have? Firefly AIBOX-K3 Board Support Request Hi, Armbian community! This is my first time writing issue here, and my understanding of embedded hardware is not very high(Actually very low) sorry 🙏 I would like to propose adding support for the Firefly AIBOX-K3, based on the SpacemiT Key Stone K3 SoC, to Armbian. I have successfully built an Armbian image using the existing spacemit-k3 board family and booted it on the actual AIBOX-K3 hardware. The initial implementation requires only a board specific configuration, without modifications to the existing spacemit-k3 family or additional kernel/Device Tree patches. Tested configuration The AIBOX K3 I tested uses the following configuration SoC: SpacemiT Key Stone K3 (RISC-V) Boot firmware: Existing Firefly OpenSBI/U-Boot in SPI NOR Boot storage: UFS UFS logical sector size: 4096 bytes Partition table: GPT Boot partition: FAT, starting at 12 MiB, size 256 MiB Root partition: ext4, starting at 268 MiB Devi
What happened? Since 0ab7e3d ("bsp: ship sysctl defaults and Provide linux-sysctl-defaults"), every RELEASE=jammy image fails when the board support package is installed into the rootfs: dpkg: error processing archive /root/armbian-bsp-cli-smartpi1-current_26.11.0_armhf__1-PCa4d1-V08e3-H9299-B0cfe-Rc5ba.deb (--unpack): trying to overwrite '/usr/lib/sysctl.d/50-default.conf', which is also in package systemd 249.11-0ubuntu3.22 E: Sub-process /usr/bin/dpkg returned an error code (1) Error context msg [ Installation of /root/armbian-bsp-cli-smartpi1-current_26.11.0_armhf__... failed smartpi1 jammy no sunxi ] Error 1 occurred in main shell at /armbian/lib/functions/rootfs/apt-install.sh:107 The BSP declares Replaces: linux-sysctl-defaults, which is the owner of that file on recent releases. On Ubuntu 22.04 the file still belongs to systemd itself (249.11), and there is no Replaces for that, so dpkg refuses the overwrite. Other releases build fine (bookworm, trixie, forky, noble, bullseye
What happened? On Orange Pi 5 with Armbian 26.8.1 (Ubuntu 26.04, kernel 6.18.43-current-rockchip64), armbian-install was used with: Boot from SPI - system on SATA, USB or NVMe The installation to NVMe completed, but the board could not boot from SPI -> NVMe. Comparing the SPI contents showed that armbian-install had flashed the SATA-specific U-Boot image: NO MATCH: u-boot-rockchip-spi.bin MATCH: u-boot-rockchip-spi-sata.bin How to reproduce? Boot Armbian 26.8.1 for Orange Pi 5 from SD. Run armbian-install. Select Boot from SPI - system on SATA, USB or NVMe. Choose an NVMe drive as the target. Complete the installation and try to boot with the SD card removed. The board fails to boot from NVMe. Compare /dev/mtd0 against the two SPI images: DIR=/usr/lib/linux-u-boot-current-orangepi5 for f in "$DIR"/u-boot-rockchip-spi*.bin; do size=$(stat -c %s "$f") if sudo cmp -s -n "$size" "$f" /dev/mtd0; then echo "MATCH: $(basename "$f")" else echo "NO MATCH: $
Task description Goal Provide a reproducible technical handoff for experimental Sony IMX219 camera support on Orange Pi 4A (Allwinner T527 / sun55i-A523 family), get maintainer feedback on the correct Armbian/upstream path, and prepare the work for a later cleaned submission after validation against the Linux/Armbian 7.3 generation. Project repository: https://github.com/nickslkr/orangepi-4a-imx219 Technical handoff: https://github.com/nickslkr/orangepi-4a-imx219/blob/main/docs/ARMBIAN_HANDOFF_2026-10-04.md Current working state The camera pipeline is operational on the tested Orange Pi 4A system. Hardware path: Sony IMX219 -> A523/T527 MIPI2 receiver / D-PHY2 -> Allwinner CSI parser / capture engine -> /dev/video0 -> RAW10 / RG10 1920x1080 The production userspace path is: /dev/video0 RG10 -> OpenCL debayer + YUV conversion on Mali-G57 via Rusticl/Panfrost -> YUV420 -> v4l2loopback /dev/video10 -> uStreamer The stable production target used during testing is app
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to armbian/build, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of armbian/build acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.4% were successfully merged into the primary branch.
armbian/build has a recorded first-timer success rate of 75.6%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 69.4 places armbian/build in the Welcoming tier.
The external pull request merge rate is 78.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, armbian/build currently has 13 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for armbian/build are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.