macOS
brew install eslintlocal Homebrew formula metadata
安装
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 的匹配本地密钥处理 manifest。Nucleus 软件包元数据仍在此发布,以便未来覆盖拥有稳定的软件包 URL。
在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。
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来源线索
此页面由 av-web 从 scripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。
View the package source record on GitHub.