pkg.soopen package index

cask

使用 Homebrew Cask 安装 google-chrome@canary

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

安装

其他安装命令

macOS

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

local Homebrew cask metadata

概览

软件包摘要

Web browser

命令和别名

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

历史

项目历史与用法

Google Chrome Canary is Google's most experimental public Chrome channel, exposing very recent changes with minimal testing and a correspondingly high risk of crashes or breakage.

项目历史

Google launched Chrome and the open-source Chromium project in September 2008. The team initially used frequently updated Dev builds to gather early feedback.

In 2010, Google added the Canary Build because even the Dev cadence was sometimes too slow for feedback. Canary was designed to update more frequently with riskier, lightly tested changes and later became part of the familiar Canary-to-Dev-to-Beta-to-Stable progression.

采用历史

Google introduced Canary for users willing to test changes even earlier than the Dev channel. Its initial announcement emphasized very frequent builds, riskier changes, little or no human verification, and side-by-side installation so a broken Canary would not displace a dependable browser.

Canary became the earliest public tier of Chrome's release pipeline. It is chiefly adopted by browser engineers, web developers, compatibility testers, and enthusiasts who value immediate access to changes over day-to-day stability.

使用方式

Use Canary for early web-platform experimentation, regression discovery, and checking changes that have not yet progressed to Dev or Beta. Google advises against using it as an everyday browser.

The current macOS build keeps its profile in a Canary-specific Application Support directory, enabling side-by-side use with other Chrome channels.

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

Canary is Chrome's classic bleeding-edge package: rapidly rebuilt from current work, deliberately isolated from safer channels, and useful for finding regressions at their earliest public stage. Its dedicated cask and profile directory let testers keep this volatile build beside production browsers.

时间线

  • 2008: Google launched Chrome and the Chromium open-source project.
  • 2010: Google introduced Chrome Canary as a more frequently updated, riskier channel than Dev.

Related projects

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

安全态势

尚未找到受保护工具覆盖

没有找到 google-chrome@canary 的匹配本地密钥处理 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 Canary

可执行文件

已安装的可执行文件

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

新鲜度

版本和新鲜度

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

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

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

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

安装元数据

软件包元数据

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

注册表事实

源数据库详情

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokengoogle-chrome@canary
Names
  • Google Chrome Canary
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