macOS
brew install eslintlocal Homebrew formula metadata
brew
eslint のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。
インストール
brew install eslintlocal Homebrew formula metadata
sudo apt install eslintDebian stable package indexes · eslint · ソース: deb.debian.org
nix profile install nixpkgs#eslintnixpkgs package indexes · pkgs/by-name/es/eslint/package.nix · ソース: api.github.com
sudo pacman -S eslintArch Linux sync databases · eslint · ソース: geo.mirror.pkgbuild.com
概要
AST-based pattern checker for JavaScript
履歴
ESLint is the dominant pluggable linter for ECMAScript and JavaScript projects. Its own README defines it as a tool for identifying and reporting patterns in JavaScript code, built around AST analysis and a runtime-pluggable rule model.
ESLint appeared on npm in 2013 and reached 1.0.0 in July 2015. The official 1.0.0 announcement described that milestone as the first major release after more than two years of work and as the stable base for future growth.
The project differentiated itself from JSLint and JSHint by using Espree for parsing, evaluating code through an AST, and making every rule pluggable. That architecture made ESLint attractive both as an end-user CLI and as a library for editor integrations, shareable configs, and custom rule packages.
Configuration has been one of ESLint's major historical arcs. The original eslintrc system accumulated multiple file formats and lookup rules; in 2022 the project introduced flat config, centered on `eslint.config.js`, as a simpler model. ESLint v9.0.0 made flat config the default and officially deprecated eslintrc.
ESLint became a default dependency in JavaScript projects because it solved both style and correctness checks through one package ecosystem. The README links npm version and download badges, Open Collective funding, official docs, rules, contribution paths, and scheduled releases, reflecting a mature tool maintained as public infrastructure.
The plugin and shareable-config model drove adoption beyond core JavaScript. React, TypeScript, framework, import-order, accessibility, security, and formatting-adjacent workflows all built on ESLint's rule API, which made `eslint` a central package in Node.js development even when a project used higher-level presets.
The official release process also shaped adoption: the project publishes scheduled releases every two weeks and documents semver policies for rule, CLI, formatter, and API changes, which matters because lint rule updates can change build outcomes.
Typical package-manager usage starts with `npm init @eslint/config@latest` and then `npx eslint yourfile.js`, while Homebrew and OS packages provide an `eslint` executable for users who install developer tools outside a project-local npm workflow.
Current ESLint configuration lives in a project-root flat config file named `eslint.config.js`, `eslint.config.mjs`, `eslint.config.cjs`, or a TypeScript variant with additional setup. Those files export configuration objects that set rules, plugins, language options, ignores, processors, and related linting behavior.
ESLint is used directly in terminals and CI, indirectly through editor integrations, and as an API consumed by other tools. Its significance in package-manager culture comes from how often it appears in `devDependencies`, lockfiles, shareable configs, monorepo lint scripts, and pre-commit or CI quality gates.
For package nerds, ESLint is a canonical example of a package ecosystem forming around a stable extension API: parser packages, plugins, config packages, formatter packages, and editor tooling all orbit the core package.
It is also one of the clearest examples of why developer-tool packages need careful semver. A minor rule behavior change can create new warnings, a major config migration can affect nearly every JavaScript project, and the project's own semver policy documents those tradeoffs explicitly.
セキュリティ状態
eslint に一致するローカルシークレット処理マニフェストは見つかりませんでした。将来の対応で安定したパッケージ URL を使えるよう、Nucleus パッケージメタデータはここに公開されています。
エージェントに無人実行させる前に、このツールが平文の認証情報を読むか、リモート状態を書き込むか、成果物を公開するか、プラグインを起動するかを確認してください。
local files
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.
Config paths the tool may read or write during local use.
PROJECT_ROOT/eslint.config.jsPROJECT_ROOT/eslint.config.mjsPROJECT_ROOT/eslint.config.cjsPROJECT_ROOT/eslint.config.tsPROJECT_ROOT/eslint.config.mtsPROJECT_ROOT/eslint.config.cts実行可能ファイル
| コマンド | 種類 | 公開範囲 | メモ |
|---|---|---|---|
eslint | cli | グローバル実行可能ファイル |
鮮度
これらの信号は、ページ生成時期、パッケージマネージャの活動、上流リリース比較を分けて示します。バージョン遅れは、証拠 URL と比較可能なバージョンがある場合だけ警告されます。
インストールメタデータ
| パッケージキー | brew:eslint |
|---|---|
| バージョン | 10.6.0 |
| パッケージマネージャ | Homebrew |
| パッケージマネージャページ | https://formulae.brew.sh/formula/eslint |
| ホームページ | https://eslint.org |
| リポジトリ | https://github.com/eslint/eslint |
| 上流ドキュメント | https://eslint.org/docs/latest |
| ライセンス | MIT |
| ソースアーカイブ | https://registry.npmjs.org/eslint/-/eslint-10.6.0.tgz |
| 最終更新 | 2026-06-27T21:36:20Z |
| Pulse | updated |
| 依存関係 | node |
| Bottle | 利用可能 (対象 all) |
| Homebrew post-install | 未定義 |
| サービス | 宣言なし |
レジストリ情報
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | eslint |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
ソースデータベース一致
一致は外部パッケージマネージャインデックスから取得され、ローカルの Automic Vault パッケージリンクとは分けて表示されます。
eslint 6.4.0~dfsg+~6.1.9-12
AST-based pattern checker for JavaScript
sudo apt install eslinteslint
nix profile install nixpkgs#eslinteslint 6.4.0~dfsg+~6.1.9-11build3
AST-based pattern checker for JavaScript
sudo apt install eslinteslint 10.0.3-1
An AST-based pattern checker for JavaScript
sudo pacman -S eslintソース経路
このページは scripts/generate-pkg-sqlite.py が生成した非公開のパッケージ SQLite アーティファクトから av-web によって提供されます。
View the package source record on GitHub.