pkg.soopen package index

cask

使用 Homebrew Cask 安装 google-chrome@beta

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

安装

其他安装命令

macOS

Homebrew Cask已验证 · 100%
brew install --cask google-chrome@beta

local Homebrew cask metadata

概览

软件包摘要

Web browser

命令和别名

本地软件包数据库中没有找到可执行别名。

历史

项目历史与用法

Google Chrome Beta is Google's comparatively low-risk preview channel for features expected to reach the Stable browser. It occupies the testing stage between the faster-moving Dev channel and Stable.

项目历史

Google launched Chrome as a Windows beta on September 2, 2008 while releasing its underlying Chromium code as an open-source project. Chrome left beta in December 2008.

Chrome for Mac entered beta in December 2009. The channel system evolved into a pipeline in which changes move through Canary, Dev, Beta, and finally Stable, gathering progressively broader testing feedback.

采用历史

Chrome's Beta channel became the preview stage immediately ahead of Stable in Google's staged release pipeline. Google currently describes it as offering roughly a four-to-six-week preview, suitable for discovering compatibility issues before a release reaches most users.

On macOS, current channel builds have distinct application identities and profile directories, allowing Beta to run alongside Stable, Dev, and Canary. This makes the Beta cask useful for cautious pre-release testing without replacing a normal browser profile.

使用方式

Use Beta to preview upcoming web-platform and browser changes, reproduce compatibility issues before Stable promotion, and validate managed-browser deployments. It is not intended to be as conservative as Stable.

Its separate macOS user-data directory allows a current side-by-side build to keep an independent profile from the other Chrome channels.

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

Beta is the conservative edge of Chrome's pre-release ecosystem: new enough for advance compatibility checks, but more tested than Dev or Canary. A separate cask and profile make switching between Stable and Beta reproducible and low-friction.

时间线

  • 2008: Google Chrome launched publicly as a beta.
  • 2008: Chrome 1.0 moved to the Stable channel.
  • 2009: Google released Chrome for Mac in beta.

Related projects

  • Google Chrome Stable
  • Google Chrome Dev
  • Google Chrome Canary
  • Chromium
  • Chrome for Testing

安全态势

尚未找到受保护工具覆盖

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

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • 未记录 Homebrew bottle 元数据。

建议审查

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

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.

macOS
~/Library/Application Support/Google/Chrome Beta

可执行文件

已安装的可执行文件

命令类型暴露范围备注
没有可执行文件数据。

新鲜度

版本和新鲜度

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

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

https://www.google.com/chrome/beta/

  • 信息No package-manager update timestamp was available.低 置信度
  • 信息Release/tag comparison is only available for GitHub repositories.https://www.google.com/chrome/beta/none 置信度

安装元数据

软件包元数据

软件包键cask:google-chrome@beta
版本159.0.8154.13
软件包管理器Homebrew Cask
软件包管理器页面https://formulae.brew.sh/cask/google-chrome@beta
主页https://www.google.com/chrome/beta/
上游文档https://www.google.com/chrome/beta/
源码归档https://dl.google.com/chrome/mac/universal/beta/googlechromebeta.dmg
SHA-256no_check
Bottle未记录
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokengoogle-chrome@beta
Names
  • Google Chrome Beta
Depends On
Artifacts
Auto Updatesyes
Deprecatedno
Disabledno

来源线索

由仓库数据生成

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

使用的来源

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment