# Install wsk with Homebrew

OpenWhisk Command-Line Interface (CLI). Version 1.2.0 via Homebrew; verified from local package data.

## Install

```sh
sudo av install brew:wsk
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install wsk
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:wsk
- **Package manager:** Homebrew
- **Version:** 1.2.0
- **Source summary:** OpenWhisk Command-Line Interface (CLI)
- **Homepage:** <https://openwhisk.apache.org/>
- **Repository:** <https://github.com/apache/openwhisk-cli>
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- wsk (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 1.2.0
## Project history and usage

`wsk` is the command-line interface for Apache OpenWhisk, the open-source serverless platform that executes functions in response to events. The CLI is the user's main shell entry point for creating, invoking, listing, and managing OpenWhisk entities against a local deployment, Apache deployment, or compatible hosted service.

Historically, `wsk` sits inside OpenWhisk's larger path from IBM Research project to Apache serverless platform. The CLI matters because serverless systems are operationally remote by nature: without a command-line client and configuration file, developers cannot conveniently target an API host, authenticate, create actions, wire triggers, or debug requests.

### Project history

OpenWhisk began as an IBM Research initiative in February 2015, according to Rodric Rabbah, who describes creating the project and leading its architecture, tooling, and runtimes. It was publicly announced in February 2016 at IBM InterConnect, launched on Bluemix and GitHub under the Apache License 2.0, and reached general availability on IBM Bluemix in December 2016 while also entering the Apache Software Foundation incubator.

The `apache/openwhisk-cli` repository was created on 3 April 2017, separating the Go-based command-line client into its own Apache repository. The GitHub README describes it as a unified tool for interacting with OpenWhisk services and documents released binaries for Linux, macOS, and Windows, plus source builds using Go and Gradle.

OpenWhisk's platform story expanded through IBM Cloud Functions, Adobe I/O Runtime, Red Hat involvement, and other deployments. Adobe's Runtime documentation states that Adobe I/O Runtime is based on Apache OpenWhisk and uses the OpenWhisk architecture to provide function-as-a-service, showing how `wsk`-style interaction fits into larger hosted serverless offerings even when vendors wrap or supplement the tooling.

### Adoption history

OpenWhisk adoption has been strongest among cloud/serverless platforms and self-hosted open-source serverless users rather than as a general-purpose programming language tool. The Apache homepage describes OpenWhisk as deployable locally or on cloud container infrastructure, with Kubernetes and Helm emphasized for developer and operator convenience.

The CLI's adoption follows the platform. Apache documentation names the OpenWhisk CLI as one of the key tools alongside the REST API, deployment utility, and language clients, and explicitly documents Homebrew installation for Linux or macOS. That makes `brew:wsk` the package-manager route for users who need the stock Apache client rather than a vendor-specific wrapper.

### How it is used

Before use, the CLI is configured with an API host and authentication key. Apache documentation shows `wsk property set --apihost API_HOST --auth AUTH_KEY --namespace guest`, and states that the CLI stores properties in `~/.wskprops` by default unless `WSK_CONFIG_FILE` points elsewhere.

Once configured, developers use `wsk` to manage OpenWhisk actions, triggers, rules, packages, APIs, and deployment helpers. The Apache homepage frames the workflow as writing functions in supported languages, targeting an OpenWhisk instance with the CLI, and running actions in response to direct invocations, HTTP requests, schedules, or external events.

### Why package nerds care

`wsk` is package-nerd significant because it is the portable client binary for an Apache serverless control plane. Package managers turn the platform's API into a normal local tool that can be installed in shells, CI images, tutorials, and operator workstations.

The CLI also captures a historical moment in serverless tooling: early function-as-a-service systems needed standalone clients that could point at hosted cloud endpoints or local developer deployments. `wsk` remains the recognizable command name for Apache OpenWhisk even when surrounding products such as IBM Cloud Functions or Adobe I/O Runtime add their own layers.

### Timeline

- 2015-02: OpenWhisk begins as an IBM Research initiative.
- 2016-02: OpenWhisk is publicly announced at IBM InterConnect and launched on Bluemix and GitHub.
- 2016-12: OpenWhisk reaches general availability on IBM Bluemix and is accepted into the Apache Software Foundation incubator.
- 2017-04-03: The `apache/openwhisk-cli` repository is created.
- 2018-08-18: `openwhisk-cli` publishes 0.9.0-incubating on GitHub.
- 2019-09-23: `openwhisk-cli` publishes 1.0.0.
- 2021-04-01: `openwhisk-cli` publishes 1.2.0.

### Related projects

- Apache OpenWhisk is the serverless platform controlled by `wsk`.
- openwhisk-wskdeploy provides deployment tooling, with functionality also embedded as `wsk deploy` in the CLI documentation.
- IBM Cloud Functions and Adobe I/O Runtime are hosted offerings or runtimes associated with OpenWhisk's adoption history.
- Kubernetes, OpenShift, Docker Compose, and Helm are common deployment technologies in the OpenWhisk ecosystem.

### Sources

- <https://api.github.com/repos/apache/openwhisk-cli>
- <https://api.github.com/repos/apache/openwhisk-cli/releases>
- <https://developer.adobe.com/app-builder/docs/get_started/runtime_getting_started/how-runtime-works>
- <https://github.com/apache/openwhisk-cli>
- <https://openwhisk.apache.org/>
- <https://openwhisk.apache.org/documentation.html>
- <https://rabbah.io/openwhisk/>


## 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: ~/.wskprops

## Credential files

- Unix: ~/.wskprops

## Combined YAML source

View the package source record on GitHub. [combined/wsk.yml](https://github.com/mxcl/pkgdb/blob/main/combined/wsk.yml)


## Sources

- 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