# Install copa with Homebrew

Tool to directly patch container images given the vulnerability scanning results. Version 0.14.2 via Homebrew; verified 2026-07-27.

## Install

```sh
sudo av install brew:copa
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install copa
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:copa
- **Package manager:** Homebrew
- **Version:** 0.14.2
- **Source summary:** Tool to directly patch container images given the vulnerability scanning results
- **Homepage:** <https://project-copacetic.github.io/copacetic/>
- **Repository:** <https://github.com/project-copacetic/copacetic>
- **Last updated:** 2026-07-27T22:04:04+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- copa (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Copa is the CLI for Project Copacetic, a Go and BuildKit-based tool for patching vulnerable container images without doing a full image rebuild.

### Project history

The official repository was created in January 2023 and released v0.1.0 the next day. The project developed around direct vulnerability patching: adding a patch layer to existing images based on scanner output rather than forcing users to rebuild from source.

### Adoption history

The official site identifies Copacetic as a CNCF Sandbox project and lists ecosystem adoption by Azure Container Registry Continuous Patching, Kubescape, Devtron, and Helmper. It also documents featured talks at KubeCon North America 2024 and OpenSSF SOSS Fusion Conference 2024.

### How it is used

Copa is commonly used in CI/CD and image-maintenance workflows. It consumes vulnerability scanning results, has built-in Trivy support, supports third-party scanners, and patches images across multiple Linux package-manager families and platforms.

### Why package nerds care

For package and container maintainers, Copa sits at the boundary between OS package updates and container distribution. It is interesting because it turns package-manager-level remediation into a post-build image operation, which can reduce rebuild churn for downstream image consumers.

### Timeline

- 2023: Official GitHub repository created.
- 2023: v0.1.0 released.
- 2024: Project featured in KubeCon and OpenSSF talks listed by the official site.
- 2026: Official site lists Copacetic as a CNCF Sandbox project.

### Related projects

- Official documentation connects Copa with BuildKit, Trivy, Azure Container Registry Continuous Patching, Kubescape, Devtron, and Helmper.

### Sources

- <https://project-copacetic.github.io/copacetic/website/>
- <https://github.com/project-copacetic/copacetic>
- <https://github.com/project-copacetic/copacetic/releases>
- <https://api.github.com/repos/project-copacetic/copacetic>


## Security Notes

infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- infrastructure mutation or orchestration signal


## Combined YAML source

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


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- cross-ecosystem install command graph