macOS
brew install --cask google-chrome@betalocal Homebrew cask metadata
cask
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für google-chrome@beta in AI-Agent-Workflows.
Installation
brew install --cask google-chrome@betalocal Homebrew cask metadata
Überblick
Web browser
In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.
Verlauf
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.
Sicherheitslage
Für google-chrome@beta 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 BetaExecutables
| 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/beta/
Installationsmetadaten
| Paketschlüssel | cask:google-chrome@beta |
|---|---|
| Version | 159.0.8154.13 |
| Paketmanager | Homebrew Cask |
| Paketmanager-Seite | https://formulae.brew.sh/cask/google-chrome@beta |
| Homepage | https://www.google.com/chrome/beta/ |
| Upstream-Dokumentation | https://www.google.com/chrome/beta/ |
| Quellarchiv | https://dl.google.com/chrome/mac/universal/beta/googlechromebeta.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@beta |
| 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.