Install falcoctl with Homebrew, Nix, zypper

Project links

• Homepage
• Package manager page

Commands and aliases

• falcoctl

Project history

The repository was created in 2019 and its first GitHub release was labeled an initial proof of concept. It later became part of the Falco project's core, stable repository set, with the README badges identifying it as both a Falco core repository and stable project.

The tool exists because Falco is no longer just one binary and one rules file. The Falco project documents falcoctl as the component that makes it easier to install rules and plugins and perform administrative tasks, and also notes that falcoctl is bundled together with Falco.

Adoption history

falcoctl's adoption is tied to Falco's ecosystem packaging. Its README documents Linux and macOS release artifacts, Homebrew installation on macOS, source builds, and the default falcosecurity artifact index at `https://falcosecurity.github.io/falcoctl/index.yaml`.

The broader Falco documentation describes Falco as a graduated CNCF project used in production by listed organizations, and names falcoctl among the main project components and ecosystem tools. That makes falcoctl important even when users encounter it indirectly through Falco packaging.

How it is used

The basic workflow begins with `falcoctl index add`, which stores index metadata locally and downloads an index file. Users then run commands such as `falcoctl index list`, `falcoctl artifact search`, and `falcoctl artifact install` to discover and install Falco rules files and plugins from registries such as GHCR.

The default system configuration file is `/etc/falcoctl/falcoctl.yaml`, while user state under `~/.config/falcoctl/` stores caches, index metadata, and OAuth2 client credentials. Registry authentication can also be configured in the YAML file for private or cloud registries.

Why package nerds care

falcoctl matters to package and runtime-security users because it separates Falco ecosystem artifact distribution from the Falco daemon itself. Instead of hand-copying rule files and plugins, operators can use a package-manager-like index and artifact model that fits CI, container, and host automation.

Timeline

• 2019: Repository created.
• 2019: v0.0.1 released as an initial proof of concept.
• 2022: README examples show the default falcosecurity artifact index workflow.
• 2026: v0.13.0 released.

Related projects

• Falco is the runtime security project falcoctl administers.
• Falco rules and plugins are the main artifact types handled by falcoctl.
• Falco Evolution tracks falcoctl as a core, stable repository.

Sources

• https://github.com/falcosecurity/falcoctl
• https://raw.githubusercontent.com/falcosecurity/falcoctl/main/README.md
• https://falco.org/docs/
• https://github.com/falcosecurity/evolution/blob/main/REPOSITORIES.md
• https://api.github.com/repos/falcosecurity/falcoctl
• https://api.github.com/repos/falcosecurity/falcoctl/releases?per_page=100