Credo
Shares rank 12 of 14 linters by recommenders
Elixir linter that enforces code style and steers LLM coding agents with deterministic checks; people pair it with dialyzer and tidewave.
Elixir linter that enforces code style and steers LLM coding agents with deterministic checks; people pair it with dialyzer and tidewave.
5 people gave an opinion
- recommend it
- 5
- criticize it
- 0
- approval share
- 100%
Recommended in 6 of 13 months
- November 2025: not recommended
- December 2025: not recommended
- January 2026: not recommended
- February 2026: recommended
- March 2026: not recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it doesn’t carry the badge
- 5 people recommend itNeeds 10 or more, not met.
- Nobody criticizes itNeeds 2 to 1 or better, met.
- Recommended in 6 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Strong style enforcement for Elixir
“The tooling for inspecting and enforcing style (tidewave, credo, dialyzer, Dan's "vibe" ecosystem tools) is far beyond what I see in other ecosystems”
Comment from 26 May 2026 in “Use Boring Languages with LLMs” “Even more so when one starts adding packages like credo, ex_slop, and boundary to run deterministically and steer the LLM.”
Comment from 14 Jun 2026 in “Phoenix LiveView 1.2 Released” Deterministic feedback loop for LLMs
“Even more so when one starts adding packages like credo, ex_slop, and boundary to run deterministically and steer the LLM.”
Comment from 14 Jun 2026 in “Phoenix LiveView 1.2 Released” “The combination of credo, dialyzer, and tidewave means you have an iterative feedback loop”
Comment from 8 Feb 2026 in “Show HN: Craftplan – Elixir-based micro-ERP for small-scale manufacturers” Extensible with custom rules
“Credo has https://github.com/elixir-vibe/ex_slop added to it.”
Comment from 10 Oct 2026 in “Next.js 16.4” “so it would be creating a custom Credo rule”
Comment from 22 Jun 2026 in “GLM 5.2 vs. Opus” Combines well with other tools
“The combination of credo, dialyzer, and tidewave means you have an iterative feedback loop”
Comment from 8 Feb 2026 in “Show HN: Craftplan – Elixir-based micro-ERP for small-scale manufacturers” “Even with my eyes constantly in the logs window, credo + ex_dna + ash_credo”
Comment from 6 Apr 2026 in “AI agents over SSH from your phone. Starting to think this is where dev is going”
Other linters people recommend
The four most recommended other linters, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Ruff | 115 | 16 | 88% | 11 | — | Approved |
| Clippy (Rust linter) | 58 | 31 | 65% | 12 | — | — |
| ESLint | 32 | 22 | 59% | 11 | — | — |
| Biome | 23 | 5 | 82% | 10 | — | Approved |
| CredoThis page | 5 | 0 | 100% | 6 | — | — |
What people said
6 of the 7 comments that mention it, newest first. Each links to the original comment.
“Credo has https://github.com/elixir-vibe/ex_slop added to it.”
“so it would be creating a custom Credo rule”
“Even more so when one starts adding packages like credo, ex_slop, and boundary to run deterministically and steer the LLM.”
“The tooling for inspecting and enforcing style (tidewave, credo, dialyzer, Dan's "vibe" ecosystem tools) is far beyond what I see in other ecosystems”
“Even with my eyes constantly in the logs window, credo + ex_dna + ash_credo”
“The combination of credo, dialyzer, and tidewave means you have an iterative feedback loop”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.