pkg.soopen package index

cask

Install google-chrome@canary with Homebrew Cask

Web browser. Version 160.0.8176.2 via Homebrew Cask; verified from local package data.

install

Additional install commands

macOS

Homebrew Caskverified · 100%
brew install --cask google-chrome@canary

local Homebrew cask metadata

overview

Package summary

Web browser

Commands and aliases

No executable aliases were found in the local package database.

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

  • 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

security posture

No protected-tool coverage found yet

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.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

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

executables

Installed executables

CommandKindExposureNote
No executable data was present.

freshness

Version and 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.

page generated2026-11-22
manager version160.0.8176.2
manager updated
local dataok
upstreamnot checked
latest detectednot detected

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

  • infoNo package-manager update timestamp was available.low confidence
  • infoRelease/tag comparison is only available for GitHub repositories.https://www.google.com/chrome/canary/none confidence

install metadata

Package metadata

Package keycask:google-chrome@canary
Version160.0.8176.2
Package managerHomebrew Cask
Package manager pagehttps://formulae.brew.sh/cask/google-chrome@canary
Homepagehttps://www.google.com/chrome/canary/
Upstream docshttps://www.google.com/chrome/canary/
Source archivehttps://dl.google.com/chrome/mac/universal/canary/googlechromecanary.dmg
SHA-256no_check
Bottlenot recorded
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

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

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

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