Install credo with Homebrew

Project links

• Homepage

Commands and aliases

• credo

Project history

The official changelog identifies version 0.1.0 as the initial release. Early releases added CLI behavior, issue categories, per-function lint support, custom checks, generated configuration, and support for project-specific .credo.exs files.

Adoption history

Credo became part of normal Elixir project hygiene because it fits the Mix workflow and publishes documentation on HexDocs. The README also documents editor and automated-code-review integrations, which helped make it useful both locally and in CI.

How it is used

The README recommends adding {:credo, "~> 1.7", only: [:dev, :test], runtime: false} to mix.exs, running mix deps.get, and then running mix credo. Configuration is usually generated or maintained in .credo.exs.

Why package nerds care

For package maintainers, Credo is the Elixir ecosystem's familiar lint-style dependency: it ships through Hex, exposes a Mix task, can fail CI through exit status, and has enough formatter and integration surface to appear in editor, CI, and code-review pipelines.

Timeline

• 0.1.0: Initial release
• 0.2.0: Added non-zero exit status when issues are found
• 0.3.0: Added per-function lint support
• 0.4.0: Added custom check support and changed .credo.exs merging behavior
• 1.0.0: Stabilized the 1.x line with documentation and breaking changes for custom checks
• 1.7.0: Added SARIF output and check IDs

Related projects

• The README lists editor integrations for JetBrains Elixir support, Atom, VS Code, flycheck, Kakoune, and Neovim/null-ls, plus Codacy for automated code review.

Sources

• https://github.com/rrrene/credo#readme
• https://hexdocs.pm/credo
• https://github.com/rrrene/credo/blob/master/CHANGELOG.md