macOS
brew install --cask google-chrome@canarylocal Homebrew cask metadata
cask
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für google-chrome@canary in AI-Agent-Workflows.
Installation
brew install --cask google-chrome@canarylocal Homebrew cask metadata
Überblick
Web browser
In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.
Verlauf
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.
Sicherheitslage
Für google-chrome@canary wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
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
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
| Es waren keine Executable-Daten vorhanden. | |||
Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
https://www.google.com/chrome/canary/
Installationsmetadaten
| Paketschlüssel | cask:google-chrome@canary |
|---|---|
| Version | 160.0.8176.2 |
| Paketmanager | Homebrew Cask |
| Paketmanager-Seite | https://formulae.brew.sh/cask/google-chrome@canary |
| Homepage | https://www.google.com/chrome/canary/ |
| Upstream-Dokumentation | https://www.google.com/chrome/canary/ |
| Quellarchiv | https://dl.google.com/chrome/mac/universal/canary/googlechromecanary.dmg |
| SHA-256 | no_check |
| Bottle | nicht erfasst |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
| Source Database | Homebrew cask API |
|---|---|
| Tap | homebrew/cask |
| Full Token | google-chrome@canary |
| Names |
|
| Depends On | |
| Artifacts | |
| Auto Updates | yes |
| Deprecated | no |
| Disabled | no |
Quellspur
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
View the package source record on GitHub.