Automic VaultAutomic Vault

brew

使用 Homebrew 安装 addons-linter

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

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install addons-linter

local Homebrew formula metadata

概览

软件包摘要

Firefox Add-ons linter, written in JavaScript

命令和别名

  • addons-linter

历史

项目历史与用法

addons-linter is Mozilla's JavaScript linter for Firefox add-ons and WebExtensions. It is both a standalone CLI and a library, and the README says it is used by web-ext and addons.mozilla.org.

项目历史

The official GitHub repository was created in September 2015 under Mozilla. The README frames the linter as infrastructure for validating packaged or unpacked WebExtensions, with output suitable for developers and for automation.

The linter's implementation is organized around scanners, rules, collectors, and reporters. The README says it relies heavily on ESLint for JavaScript, cheerio for HTML parsing, and Fluent tooling for language packs. As of November 2021, Mozilla's dispensary library-detection work was merged into the project and exposed through a CLI script.

采用历史

Official adoption is unusually direct: Mozilla documents that addons-linter is used by web-ext and addons.mozilla.org. That makes it part of the normal Firefox extension development and submission path, not just an optional local lint command.

The package is published for Node users and packaged by Homebrew in the supplied metadata. The repository API shows an active Mozilla project with GitHub Pages documentation and regular tags through the 9.x and 10.x series.

使用方式

Developers install it globally from npm or use the packaged binary, then run addons-linter against an XPI/ZIP file or an extension source directory. It reports errors, warnings, notices, metadata, and JSON output for automation.

Library users can create a linter instance directly from JavaScript, pass config that mirrors CLI options, and consume structured linter results. The README also documents privileged-extension behavior behind the --privileged flag.

为什么软件包爱好者会关心

addons-linter matters to package people because it is validation tooling at the boundary between a source tree and a distributable browser add-on. It encodes platform policy, extension packaging expectations, and submission-time checks in a reusable CLI that downstream package managers can install like any other development tool.

时间线

  • 2015-09: GitHub repository created.
  • 2021-11: dispensary was merged into addons-linter, according to the README.
  • Current README: Node.js v22 or greater is required for development.

Related projects

  • web-ext is documented as a consumer.
  • addons.mozilla.org / addons-server is documented as a consumer.
  • dispensary was merged into the repository.

安全态势

尚未找到受保护工具覆盖

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

安装行为

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

建议审查

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

可执行文件

已安装的可执行文件

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

新鲜度

版本和新鲜度

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

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

https://github.com/mozilla/addons-linter

安装元数据

软件包元数据

软件包键brew:addons-linter
版本10.9.0
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/addons-linter
主页https://github.com/mozilla/addons-linter
仓库https://github.com/mozilla/addons-linter
上游文档https://github.com/mozilla/addons-linter#readme
许可证MPL-2.0
源码归档https://registry.npmjs.org/addons-linter/-/addons-linter-10.9.0.tgz
最后更新2026-07-14T14:59:57Z
Pulseupdated
依赖node
Bottle可用 (于 all)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

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

来源线索

由仓库数据生成

此页面由 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 package history
  • package relationship graph
  • package version freshness
  • package-page enrichment