# Install jfrog-cli with Homebrew Command-line interface for JFrog products. Version 2.117.0 via Homebrew; verified 2026-07-30. ## Install ```sh sudo av install brew:jfrog-cli ``` ## Agent safety answer jfrog-cli manages Artifactory, packages, builds, and release artifacts. - **Credential access:** Reads JFrog tokens, server config, and repository credentials. - **Remote mutation:** Can upload, delete, promote, and configure artifacts or repositories. - **Publish/artifact risk:** Can publish build artifacts and release bundles. - **Recommended control:** Gate upload, delete, promote, config, and token commands. - **Agent-use guidance:** Allow searches; require approval for artifact writes, deletes, and promotion. Additional install commands: ### macOS - Homebrew (100%): ```sh brew install jfrog-cli ``` Evidence: provider-native install command ## Package facts - **Package key:** brew:jfrog-cli - **Package manager:** Homebrew - **Version:** 2.117.0 - **Source summary:** Command-line interface for JFrog products - **Homepage:** - **Repository:** - **Last updated:** 2026-07-30T15:28:07Z - **Generated:** 2026-08-03T00:40:33+00:00 ## Executables - jf (alias) - jfrog (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 2.117.0 ## Project history and usage JFrog CLI is the command-line client for automating JFrog platform workflows. Its role is to turn Artifactory, Xray, Distribution, Access, build-info, and package-manager operations into scriptable commands for CI systems and release pipelines. ### Project history The public jfrog/jfrog-cli repository was created in 2015, and the first GitHub release series appeared in 2016. The README describes the tool as a compact client for automating JFrog product access through REST APIs, with early emphasis on reliable artifact upload and download, checksum optimization, dry runs, and wildcard or regular-expression based file selection. The release stream expanded from Artifactory-centered artifact operations into wider software-supply-chain work. The 2021 v2 line added and reorganized Xray scanning and audit commands, while later releases continued to add package ecosystem integrations, build-info handling, plugin support, and container-related workflows. ### Adoption history JFrog CLI became a natural package-manager target because it is a single executable used by build agents and developer laptops. Homebrew, Chocolatey, Scoop, winget, Linux distro packages, and JFrog's own install paths make it easy to pin in automation without embedding product-specific REST calls in every script. Its adoption follows JFrog Artifactory's role as an artifact repository in CI/CD. Teams using Maven, Gradle, npm, Docker, NuGet, Python, and Go package flows can use one CLI surface to publish artifacts, collect build metadata, promote builds, and run security or compliance scans. ### How it is used Typical use centers on configuring a JFrog server, uploading and downloading artifacts, resolving dependencies, publishing build-info, scanning builds or packages with Xray, and promoting or distributing release artifacts. The `jf` executable is the shorter command name used alongside the older `jfrog` command. The package is especially common in CI jobs because it can replace hand-written REST calls with commands that understand checksums, retries, build metadata, and package-manager conventions. ### Why package nerds care For package people, JFrog CLI is interesting because it sits at the boundary between language package managers and an enterprise artifact repository. It packages a large amount of repository-specific behavior into a portable CLI that can be installed by the same package managers it automates. It also shows how artifact-management CLIs evolved from simple upload/download helpers into supply-chain tools that collect provenance, drive scans, and coordinate release promotion. ### Timeline - 2015: The public jfrog/jfrog-cli repository was created on GitHub. - 2016: JFrog CLI 1.0.1 was tagged and released. - 2021: The v2 release stream added Xray scan and audit commands and the shorter `jf` command style. - 2022: Release notes show continued expansion around Docker, .NET, plugins, operational risk data, and build-info workflows. ### Related projects - JFrog Artifactory is the central repository service automated by the CLI. - JFrog Xray supplies the scan and audit workflows exposed through CLI commands. - JFrog build-info tooling and jfrog-client-go provide related libraries and metadata plumbing used by the CLI. ### Sources - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## 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: ~/.jfrog/jfrog-cli.conf.v6 ## Credential files - Unix: ~/.jfrog/jfrog-cli.conf.v6 ## Combined YAML source View the package source record on GitHub. [combined/jfrog-cli.yml](https://github.com/automic-vault/db/blob/main/combined/jfrog-cli.yml) ## Sources - Nucleus package database - Geiger risk classifier - curated configuration and credential file locations - curated package history - pkgdb category and tag curation - curated agent safety answer