# Installer credo avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de credo pour les workflows d'agents IA.

## installation

```sh
sudo av install brew:credo
```

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install credo
```

  Preuve: local Homebrew formula metadata

## Faits du paquet

- **Clé du paquet:** brew:credo
- **Gestionnaire de paquets:** Homebrew
- **Version:** 1.7.19
- **Résumé source:** Static code analysis tool for the Elixir
- **Page d'accueil:** <https://github.com/rrrene/credo>
- **Dépôt:** <https://github.com/rrrene/credo>
- **Dernière mise à jour:** 2026-06-13T01:24:09+02:00
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- credo (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 1.7.19
## Historique du projet et usages

Credo is an Elixir static analysis tool focused on teaching and code consistency. It is commonly added as a Mix development/test dependency and run with mix credo to report refactoring opportunities, complex code, common mistakes, naming inconsistencies, and style issues.

### Historique du projet

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.

### Historique d'adoption

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.

### Modes d'utilisation

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.

### Pourquoi les passionnés de paquets s'y intéressent

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.

### Chronologie

- 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>


## Notes de sécurité

narrow executable package without higher-risk signals.

- **Risque Geiger:** vert / faible
- 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: .credo.exs, config/.credo.exs

## Combined YAML source

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