Automic VaultAutomic Vault

brew

使用 Homebrew, apt, Nix, pacman 安装 eslint

查看 eslint 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install eslint

local Homebrew formula metadata

Linux

Debian apt已验证 · 92%
sudo apt install eslint

Debian stable package indexes · eslint · 来源: deb.debian.org

Nix已验证 · 92%
nix profile install nixpkgs#eslint

nixpkgs package indexes · pkgs/by-name/es/eslint/package.nix · 来源: api.github.com

Arch Linux pacman已验证 · 92%
sudo pacman -S eslint

Arch Linux sync databases · eslint · 来源: geo.mirror.pkgbuild.com

概览

软件包摘要

AST-based pattern checker for JavaScript

命令和别名

  • eslint

历史

项目历史与用法

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.

时间线

  • 2013: ESLint first appears on npm.
  • 2015: ESLint 1.0.0 released as the first major release.
  • 2022: Flat config introduced publicly as a new configuration system.
  • 2024: ESLint 9.0.0 makes flat config the default and deprecates eslintrc.
  • 2026: ESLint 10.x releases continue the scheduled release cadence.

Related projects

  • ESLint is historically compared with JSLint and JSHint, and its ecosystem intersects with Espree, typescript-eslint, Babel parser integrations, eslint-plugin-react, Prettier, editor integrations, and shareable config packages.

安全态势

尚未找到受保护工具覆盖

没有找到 eslint 的匹配本地密钥处理 manifest。Nucleus 软件包元数据仍在此发布,以便未来覆盖拥有稳定的软件包 URL。

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 1 个平台目标。
  • 安装时包含 1 个运行时依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

local files

Configuration and credential file locations

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.

Configuration files

Config paths the tool may read or write during local use.

Unix
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

可执行文件

已安装的可执行文件

命令类型暴露范围备注
eslintcli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-07-10
管理器版本10.6.0
管理器更新时间2026-06-27
本地数据OK
上游not checked
检测到的最新版本未检测到

https://eslint.org

  • 信息Release/tag comparison is only available for GitHub repositories.https://eslint.orgnone 置信度

安装元数据

软件包元数据

软件包键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
Pulseupdated
依赖node
Bottle可用 (于 all)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nameeslint
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

源数据库匹配

其他软件包管理器记录

匹配项来自外部软件包管理器索引,并与本地 Automic Vault 软件包链接分开显示。

Debian apt95%

eslint 6.4.0~dfsg+~6.1.9-12

AST-based pattern checker for JavaScript

https://eslint.org/

sudo apt install eslint
  • Section: javascript
  • Architecture: all
  • 32 依赖
  • 3 提供
  • 8 可选依赖
  • normalized package name match
  • 匹配方式:Eslint
Debian stable package indexes · deb.debian.org · Debian stable package indexes: eslint from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz
Nix95%

eslint

nix profile install nixpkgs#eslint
  • normalized package name match
  • 匹配方式:Eslint
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/es/eslint/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
Ubuntu apt95%

eslint 6.4.0~dfsg+~6.1.9-11build3

AST-based pattern checker for JavaScript

https://eslint.org/

sudo apt install eslint
  • Section: universe/javascript
  • Architecture: all
  • 32 依赖
  • 3 提供
  • 8 可选依赖
  • normalized package name match
  • 匹配方式:Eslint
Ubuntu 24.04 LTS package indexes · archive.ubuntu.com · Ubuntu 24.04 LTS package indexes: eslint from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz
pacman95%

eslint 10.0.3-1

An AST-based pattern checker for JavaScript

https://eslint.org

sudo pacman -S eslint
  • License: MIT
  • Architecture: any
  • 2 依赖
  • normalized package name match
  • 匹配方式:Eslint
Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: eslint from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment