// the take
A grab-bag of Chef cookbooks and legacy Python scripts Meta uses to manage its own client fleet (macOS, Windows, Linux). Useful for IT/sysadmin teams already running Chef who want prebuilt policy management for things like Chrome settings, AppLocker, Munki, Flatpak, and kernel channel pinning.
Wide cross-platform coverage in one place — Chrome policy, AppLocker, dconf, Flatpak, GNOME Software, kernel channels, and macOS profiles are all handled with dedicated, independent cookbooks you can pick individually. Most cookbooks ship with rspec specs and run through CI (rubocop + foodcritic), so there's actual test coverage behind the recipes, not just documentation promises. Cookbooks are decoupled from each other via fb_helpers/cpe_helpers rather than one monolithic recipe, so adopting one piece doesn't force you into the rest.
Everything here assumes you're already running Chef, which is itself a declining choice for new fleet management work — you're adopting two aging dependencies at once. Several cookbooks (cpe_init's company_init.rb, fb_helpers) bake in Facebook-specific assumptions about node structure and internal services that you'll have to strip out or reimplement before anything works against your own infrastructure. The legacy/ directory mixes in unmaintained Python tools (Adobe packaging, AutoDMG, AutoPkg) with no indication of what's still safe to use versus abandoned, which is a trap for anyone browsing by file name rather than commit history. The README is essentially two old conference talk links — there's no actual setup guide for wiring these cookbooks into a Chef server that isn't Meta's.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →