ESLint Ships Official Shell Script Linting Plugin, Extending Its Multi-Language Push With ShellCheck-Inspired Rules
ESLint's new official @eslint/shell plugin adds ShellCheck-inspired rules for Bash, POSIX sh and mksh scripts, extending a push that already covers JSON, Markdown and CSS.
Overview
ESLint now officially supports linting shell scripts, according to the ESLint blog, which announced the @eslint/shell plugin on November 6, 2026. The post frames the release as “another step towards providing a language-agnostic platform for source code linting,” noting that ESLint had previously added official support for JSON, Markdown, and CSS since outlining that broader goal, according to the ESLint blog.
What We Know
The @eslint/shell plugin is “an officially supported language plugin for ESLint,” according to the ESLint blog, which adds that it “provides parsing for shell scripts, a set of rules inspired by ShellCheck, and a recommended configuration.” It is installed via npm install --save-dev eslint @eslint/shell and requires Node.js ^20.19.0 || ^22.13.0 || >=24, tested against ESLint v10, according to the plugin’s GitHub repository.
The plugin supports three shell dialects through separate ESLint “languages”: shell/bash, used by the recommended configuration; shell/posix, for POSIX sh without Bash extensions; and shell/mksh, for the MirBSD Korn shell, according to the ESLint blog and the GitHub repository.
According to the GitHub repository, the plugin currently ships ten rules, each tied to a specific ShellCheck diagnostic code. They cover legacy backtick command substitution (mapped to ShellCheck’s SC2006), unquoted variable expansions subject to word splitting and globbing (SC2086/SC2046), expressions that fail to expand inside single quotes (SC2016), iterating over ls output instead of using globs (SC2045), unused variables (SC2034), piping from a single-file cat (SC2002), wrapping echo in a needless subshell (SC2116), placing variables directly in printf format strings (SC2059), failing to guard a cd command’s failure with || exit (SC2164), and using read without the -r flag, which can mangle backslashes (SC2162). Several of the rules, including the backtick and unquoted-expansion checks, are auto-fixable, and the single-quote-expansion rule is the only one of the ten enabled at the warning level rather than as an error in the recommended configuration, the repository’s rule table shows.
The plugin’s parser is “built on mvdan-sh, the parser used by shfmt,” according to the ESLint blog, and it produces an “ESTree-style syntax tree” that ESLint rules can traverse the same way they traverse JavaScript, the blog post says, meaning developers can write custom shell-linting rules using ESLint’s existing rule APIs.
The package’s version history on GitHub shows the plugin was tagged at version 0.1.0 on November 3, 2026, three days before the public announcement, with two further point releases, 0.1.1 and 0.1.2, tagged minutes apart on November 6, 2026 — the same day as the blog post — according to the GitHub releases page. The ESLint blog post is credited to Nicholas C. Zakas of the ESLint Technical Steering Committee, according to the ESLint blog.
The recommended configuration “uses Bash and enables rules that catch common problems, such as unquoted expansions, unused variables, and unsafe read usage,” the ESLint blog post says. The blog post frames shell scripts as “an important part of many projects, from build and release automation to local development tools,” and says the plugin lets developers “lint shell scripts alongside the rest of your code using ESLint’s configuration system and familiar rule APIs.”
The move extends a broader multi-language push inside the JavaScript tooling ecosystem: ESLint’s own expansion into JSON, Markdown, and CSS linting predates this release, and other JavaScript-ecosystem linters have been expanding their own scope, as previously reported when Biome shipped type-aware JavaScript linting without relying on the TypeScript compiler.
What We Don’t Know
The ESLint blog post does not specify how many of the ten rules originated in the initial 0.1.0 release versus the two point releases that followed on November 6, nor does it give a timeline for adding further ShellCheck-equivalent rules beyond the ten currently documented. The blog post and repository also do not disclose adoption figures or state whether any major open-source projects have adopted the plugin yet.
Technical Note
The plugin supports ESLint’s standard inline disable comments inside shell scripts, such as # eslint-disable-next-line shell/no-backticks, according to the GitHub repository, allowing teams to suppress individual findings the same way they do in JavaScript files.