macOS
brew install --cask google-chrome@canarylocal Homebrew cask metadata
cask
Web browser. Version 160.0.8176.2 via Homebrew Cask; verified from local package data.
install
brew install --cask google-chrome@canarylocal Homebrew cask metadata
overview
Web browser
No executable aliases were found in the local package database.
history
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.
security posture
No matching local secret-handling manifest was found for google-chrome@canary. Package metadata is still published here so future coverage has a stable package URL.
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
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.
Config paths the tool may read or write during local use.
~/Library/Application Support/Google/Chrome Canaryexecutables
| Command | Kind | Exposure | Note |
|---|---|---|---|
| No executable data was present. | |||
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
https://www.google.com/chrome/canary/
install metadata
| Package key | cask:google-chrome@canary |
|---|---|
| Version | 160.0.8176.2 |
| Package manager | Homebrew Cask |
| Package manager page | https://formulae.brew.sh/cask/google-chrome@canary |
| Homepage | https://www.google.com/chrome/canary/ |
| Upstream docs | https://www.google.com/chrome/canary/ |
| Source archive | https://dl.google.com/chrome/mac/universal/canary/googlechromecanary.dmg |
| SHA-256 | no_check |
| Bottle | not recorded |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
| Source Database | Homebrew cask API |
|---|---|
| Tap | homebrew/cask |
| Full Token | google-chrome@canary |
| Names |
|
| Depends On | |
| Artifacts | |
| Auto Updates | yes |
| Deprecated | no |
| Disabled | no |
source trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.