Linters

Your linters, in the same review. Bring style, error, and maintainability checks into CloudAEye code review, with 14 supported linters for code, Dockerfiles, scripts, and config files.

Book a demo All use cases

Lint findings beside review findings.

Incorporate linting best practices, such as style consistency, error detection, and maintainability checks to keep your codebase cleaner, more readable, and easier to maintain.

GitHubpayments-api #318

Supported linters

Area Linters
JavaScript, TypeScript ESLint, Biome
Python Ruff, Pylint, Flake8
Go GolangCI-Lint
Java Checkstyle
Kotlin detekt, ktlint
Docker Hadolint
Bash ShellCheck
YAML yamllint
Markdown markdownlint
GitHub Actions actionlint

In the review output

Linter Findings3 findings
  1. 1Unused import os.Ruffpayments/retry.py:2
  2. 2Variable attempts is assigned but never used.ESLintweb/src/retry.ts:14
  3. 3Pin package versions in apt-get install.HadolintDockerfile:7

All linter findings are grouped together, apart from the review's own findings.

Clean code,
without a second tool.

Linters catch what reviewers should not spend time on. CloudAEye runs the linters you choose as part of the review, so style and maintainability issues arrive with everything else.

14 linters, one review.

ESLint, Biome, Ruff, Pylint, Flake8, GolangCI-Lint, Checkstyle, detekt, ktlint, Hadolint, ShellCheck, yamllint, markdownlint, and actionlint.

  • StyleConsistency
  • ErrorsDetected early
  • MaintainabilityChecked on every PR
See the list

Grouped, not scattered.

Linter results are aggregated into one Linter Findings group, so they never bury the review's own findings.

  • OutputLinter Findings group
  • AlongsideBug and security findings
  • EnabledPer repository
Read the docs

Beyond application code.

Lint the files around your code too: Dockerfiles, shell scripts, YAML, Markdown, and GitHub Actions workflows.

  • DockerfilesHadolint
  • Shell and YAMLShellCheck, yamllint
  • Workflowsactionlint
See the list

Configured per repository.

Choose which linters run for each repository, and adjust them from the Linters Management page.

  • WhereLinters Management
  • ScopePer repository
  • AdjustEnable or tune each linter
Set it up

Set it up.

Turn linters on for each repository from the CloudAEye console.

Read the setup guide
  1. In Code Review, open Integrations, then Repos for your code platform.
  2. Expand Integrated Repositories.
  3. In the Linters column, click the link for the repository.
  4. On the Linters Management page, enable or adjust a linter, then click Save Changes.