Peacock isn't one program. It's a set of pieces that fit together to take a phone from factory-locked to fully yours. Here's what each one does, and where to find it.
The core. It builds a complete, device-specific OS image and is the base system that runs on the phone, with a Linux distro of your choice layered on top. Includes the builder, command line and GUI, that turns a device pick into something you can flash.
View on GitHub → Packages · CPeacock's package manager. Installs and updates the platform, your apps and compatibility layers from signed binaries, and keeps them separate from the OS underneath so swapping the distro doesn't touch your stuff.
View on GitHub → Recipes · CThe recipe tree. Every package and device kernel is defined here as a build script, so the builder knows how to compile and assemble everything that ends up in an image.
View on GitHub → Early boot · ShellBuilds the initramfs, the small environment that comes up first at boot, mounts the system and hands off to it. Produces the archive and boot scripts that the Peacock CLI flashes.
View on GitHub → Chainloader · MediaTekA tiny chainloader for MediaTek phones, heavily inspired by lk2nd. It runs right after the bootloader and hands control to Peacock or the recovery system.
View on GitHub → Bootloader · QualcommOur fork of lk2nd, the established secondary bootloader for Qualcomm phones. It loads Peacock or recovery through extlinux.
View on GitHub → Recovery · ShellThe Peacock Recovery Project. A self-contained rescue system that boots on its own when the main OS won't start, so you can repair, reinstall or roll back right from the device.
View on GitHub → Kernels · per deviceEvery supported phone gets its own kernel, forked and patched so Peacock can boot on it. The lead device today is the Oppo A16, and more land as the project grows.
Browse the repos →That's the public set. It all lives in the open. Browse the full org on GitHub.