Biome vs Hadolint

Biome is a toolchain for maintaining the health of web projects. It formats JavaScript, TypeScript, JSX, TSX, JSON, HTML, CSS, and GraphQL, and provides lint rules for JavaScript, TypeScript, JSX, CSS, and GraphQL. Linting can report diagnostics and apply safe fixes. Its check command can format files, lint them, and organize imports in one run. Biome is distributed as a standalone executable, so it does not require Node.js. Installation instructions cover npm, pnpm, bun, deno, and yarn. First-party editor extensions are available for VS Code, IntelliJ, and Zed; community extensions include Vim, Neovim, and Sublime Text. The getting-started guide links to CI integrations for GitHub Actions and GitLab CI. Biome describes itself as open source and lists MIT or Apache 2.0 licensing. The open-source toolchain is free. Contributors may offer commercial support, but requests depend on their availability.

Hadolint is a free Dockerfile linter that parses files into an abstract syntax tree and checks that structure for errors and stated best practices. It uses ShellCheck to inspect Bash code inside Dockerfile RUN instructions. Rules carry either the DL prefix for Hadolint checks or SC for ShellCheck checks. Users can ignore rules, override severity, set failure thresholds, choose report formats, and configure label schemas and trusted registries. Output formats include tty, JSON, Checkstyle, Code Climate, GitLab Code Climate, GNU, Codacy, SonarQube, SARIF, and JUnit. Hadolint runs in Docker or Podman containers and is available as a pre-commit hook. Prebuilt binaries support Linux, macOS, and Windows; installation options include Homebrew, Scoop, Nix, containers, and source builds. Documented integrations cover major CI systems and editors. An online version is hosted at hadolint.github.io/hadolint. The latest listed release is v2.15.1, under GPL-3.0.