Automic VaultAutomic Vault

brew

使用 Homebrew, winget 安装 appium

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

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install appium

local Homebrew formula metadata

Windows

Windows Package Manager已验证 · 92%
winget install --id JSFoundation.Appium -e

Windows Package Manager source index · JSFoundation.Appium · 来源: cdn.winget.microsoft.com

概览

软件包摘要

Automation for Apps

命令和别名

  • appium

历史

项目历史与用法

Appium is an open-source WebDriver-based automation framework for native, hybrid, mobile web, desktop, and other app platforms. Its package-manager identity is a Node.js CLI server plus an ecosystem of separately installed drivers, clients, and plugins.

项目历史

The Appium project grew from the idea that mobile app automation should use the same open WebDriver protocol that had become central to browser automation. The official docs state that Appium's initial goals were iOS and Android automation, and that Appium adopted WebDriver rather than inventing a new API.

The npm package history records Appium 1.0.0 in May 2014. Appium 2.0.0 was published in July 2023 after a long beta series, and the upstream changelog records Appium 3.0.0 in August 2025.

采用历史

Appium became a standard fixture in mobile QA stacks because tests can be written in WebDriver-compatible client libraries rather than platform-native test languages only. The README lists official client support for Java, Python, Ruby, and .NET C#, with third-party clients for other languages.

The project's adoption model changed significantly with Appium 2: drivers and plugins became extensions installed and updated through the Appium CLI rather than everything being bundled into one server package. That made the Homebrew formula useful as an entry point to the server while real platform support moved into extension management.

使用方式

A typical install starts the Appium server with `appium` or `appium server`, then installs a platform driver such as an iOS, Android, macOS, or Windows driver with `appium driver install`. Test suites connect over WebDriver using a language client.

Configuration can be auto-discovered from `.appiumrc.*`, `appium.config.*`, `.appiumrc`, or an `appium` property in `package.json`; Appium searches upward from the current working directory and also supports `appium --config /path/to/config/file`.

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

Appium is a good example of a CLI package whose real payload is an extension ecosystem. The formula installs the command, but the working toolchain is assembled from npm-distributed drivers and plugins plus language-specific test clients.

For packagers, Appium also marks the tension between system package managers and upstream Node distribution: the README says npm is the supported installation method, while Homebrew packages it for developers who expect a global `appium` command alongside other testing tools.

时间线

  • 2014: npm registry records Appium 1.0.0 publication.
  • 2021: Appium 2.0.0 beta series appears in the upstream changelog.
  • 2023: npm registry records Appium 2.0.0 publication.
  • 2025: Upstream changelog records Appium 3.0.0.

Related projects

  • Selenium and WebDriver are the protocol lineage Appium deliberately follows.
  • Appium Inspector is the related official GUI used to inspect app UI trees while developing tests.
  • Official and third-party Appium drivers provide platform-specific automation for iOS, Android, macOS, Windows, and other targets.

安全态势

风险级别:orange

formula declares a Homebrew service.

风险分类器

orange 风险 · 中 置信度 · infrastructure

原因

  • formula declares a Homebrew service

信号

  • metadata:service

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • formula 元数据声明了服务或守护进程块。
  • Homebrew bottle 元数据适用于 6 个平台目标。
  • 安装时包含 4 个运行时依赖。
  • 构建元数据列出 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
.appiumrc.json.appiumrc.yaml.appiumrc.yml.appiumrc.js.appiumrc.cjsappium.config.jsappium.config.cjs.appiumrcpackage.json appium property
Windows
.appiumrc.json.appiumrc.yaml.appiumrc.yml.appiumrc.js.appiumrc.cjsappium.config.jsappium.config.cjs.appiumrcpackage.json appium property

可执行文件

已安装的可执行文件

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

新鲜度

版本和新鲜度

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

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

https://appium.io/

  • 信息Release/tag comparison is only available for GitHub repositories.https://appium.io/none 置信度

安装元数据

软件包元数据

软件包键brew:appium
版本3.5.2
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/appium
主页https://appium.io/
仓库https://github.com/appium/appium
上游文档https://appium.io/docs/en/latest
许可证Apache-2.0
源码归档https://registry.npmjs.org/appium/-/appium-3.5.2.tgz
最后更新2026-06-22T14:02:44-07:00
Pulseupdated
依赖gettext, glib, node, vips
构建依赖pkgconf
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install未定义
服务declared

注册表事实

源数据库详情

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

源数据库匹配

其他软件包管理器记录

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

winget95%

JSFoundation.Appium

winget install --id JSFoundation.Appium -e
  • normalized package name match
  • 匹配方式:Appium
Windows Package Manager source index · cdn.winget.microsoft.com · Windows Package Manager source index: JSFoundation.Appium from https://cdn.winget.microsoft.com/cache/source.msix

来源线索

由仓库数据生成

此页面由 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