# Install cycode with Homebrew

Boost security in your dev lifecycle via SAST, SCA, Secrets & IaC scanning. Version 3.18.0 via Homebrew; verified 2026-07-24.

## Install

```sh
sudo av install brew:cycode
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install cycode
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:cycode
- **Package manager:** Homebrew
- **Version:** 3.18.0
- **Source summary:** Boost security in your dev lifecycle via SAST, SCA, Secrets & IaC scanning
- **Homepage:** <https://github.com/cycodehq/cycode-cli>
- **Repository:** <https://github.com/cycodehq/cycode-cli>
- **Last updated:** 2026-07-24T12:07:28Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- cycode (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Cycode CLI is a local and CI-oriented security scanner for Cycode users, covering secrets, infrastructure-as-code misconfigurations, SCA vulnerabilities, and SAST findings.

### Project history

The cycode-cli repository was created in July 2022 and published early releases later that year. Its README has grown from a scanner guide into a broader command-line manual covering authentication, configuration, pre-commit and pre-push hooks, repository and path scans, SBOM reports, and an experimental MCP server.

### Adoption history

Official installation paths include PyPI, Homebrew, and GitHub Releases, which lets teams choose between Python packaging, macOS package management, and standalone executables. The README also documents pre-commit integration, making the CLI part of developer workflow rather than only a central CI scanner.

### How it is used

Users authenticate with cycode auth, cycode configure, or environment variables, then run scans over repositories, paths, commit history, pre-commit, or pre-push contexts. The CLI stores global credentials and URLs under the user's .cycode directory and local ignore rules in .cycode/config.yaml where scans are run.

### Why package nerds care

For package maintainers, Cycode CLI is a security SaaS client with real local state: packaging needs to expose the cycode executable cleanly while leaving credentials, service URLs, and ignore-rule config in user- or project-owned YAML files.

### Timeline

- 2022: Repository created and early 0.1.x releases published.
- 2023: 0.2.x releases continued the CLI line.
- 2026: 3.x releases remained active with scanner and workflow features documented in the README.

### Related projects

- The CLI integrates with pre-commit and with Cycode's hosted service through client credentials, OIDC tokens, and Cycode API and app URLs.

### Sources

- <https://github.com/cycodehq/cycode-cli/blob/main/README.md>
- <https://api.github.com/repos/cycodehq/cycode-cli>
- <https://github.com/cycodehq/cycode-cli/releases>
- <https://formulae.brew.sh/formula/cycode>


## Security Notes

No matching local secret-handling manifest was found for cycode. Nucleus package metadata is still published here so future coverage has a stable package URL.



## 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: ~/.cycode/config.yaml, ./.cycode/config.yaml

## Credential files

- Unix: ~/.cycode/credentials.yaml

## Combined YAML source

View the package source record on GitHub. [combined/cycode.yml](https://github.com/mxcl/pkgdb/blob/main/combined/cycode.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