# osctrl-cli mit Homebrew installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für osctrl-cli in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:osctrl-cli ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install osctrl-cli ``` Evidenz: local Homebrew formula metadata ## Paketfakten - **Paketschlüssel:** brew:osctrl-cli - **Paketmanager:** Homebrew - **Version:** 0.5.4 - **Quellzusammenfassung:** Fast and efficient osquery management - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-07-27T23:46:53+02:00 - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - osctrl-cli (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 0.5.4 ## Projektgeschichte und Nutzung osctrl-cli is the operator CLI for osctrl, a Go-based osquery management platform. osctrl implements osquery's remote API as a TLS endpoint and includes services for enrollment, configuration distribution, log collection, on-demand queries, file carving, an API, web UI, and CLI automation. ### Projektgeschichte GitHub records jmpsec/osctrl as created on 2018-12-17. The project grew as a fleet-management layer for osquery, with osctrl-cli living alongside osctrl-tls, osctrl-admin, and osctrl-api as one of the built components. Release notes show continued operational hardening: v0.4.9 introduced a breaking move to a single YAML configuration file, v0.5.0 included osctrl-cli and API fixes plus security policy work, and v0.5.3 shipped osctrl-cli binary packages among its release assets. The README also labels the old server-rendered osctrl-admin interface as legacy and presents the newer frontend as the primary operator UI. ### Adoptionsgeschichte The README says osctrl is used in production environments while still under active development, and claims scalability from hundreds to hundreds of thousands of nodes. Public evidence points to a specialized endpoint-security audience rather than mass-market adoption: osquery operators, incident-response teams, and security engineers who need fleet visibility and remote querying. ### Wie es verwendet wird The osctrl-cli documentation says its purpose is to execute actions in osctrl without directly accessing the backend or using the admin interface, making it useful for scripts and automation. In the repository architecture, operators and automation can talk through osctrl-cli to the API, while some modes can work directly with the database. Operators use the broader osctrl system to enroll osquery agents, distribute configuration, collect status and result logs, run on-demand queries, and carve files. osctrl-cli is the package-friendly command-line entry point for those actions. ### Warum Paket-Nerds sich dafür interessieren osctrl-cli matters because it packages a security-operations control plane into installable binaries and Debian packages. For package nerds, it is a reminder that some CLIs are not standalone products; they are automation handles for a larger service suite with databases, TLS endpoints, log sinks, and web frontends. ### Zeitleiste - 2018-12-17: GitHub repository created. - 2025-12-24: v0.4.9 release introduced a breaking single-YAML configuration change. - 2026-02-24: v0.5.0 release included osctrl-cli/API fixes and security policy work. - 2026-06-12: v0.5.3 release published osctrl-cli Debian package assets for Linux amd64 and arm64. ### Related projects - osquery is the endpoint agent and query engine that osctrl manages. osctrl-tls implements the remote API endpoint, osctrl-api exposes REST automation, osctrl-admin and the frontend provide UI surfaces, and osctrl-cli is the command-line automation surface. ### Quellen - - - - - - - - ## Sicherheitshinweise Für osctrl-cli wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat. ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: osctrl-api.json ## Credential files - Unix: osctrl-api.json ## Combined YAML source View the package source record on GitHub. [combined/osctrl-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/osctrl-cli.yml) ## Quellen - pkg.so package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - cross-ecosystem install command graph