macOS
brew install --cask google-chrome@devlocal Homebrew cask metadata
cask
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für google-chrome@dev in AI-Agent-Workflows.
Installation
brew install --cask google-chrome@devlocal Homebrew cask metadata
Überblick
Web browser
In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.
Verlauf
Google Chrome Dev is Google's fast-moving developer preview channel, intended to expose current browser work earlier than Beta while receiving more testing than Canary.
Google launched Chrome and the underlying open-source Chromium project in September 2008. A Dev channel was already part of the distribution model when Chrome 1.0 reached Stable in December 2008.
Chrome's release engineering matured into a staged pipeline. Changes surface first in Canary, move through Dev and Beta, and reach Stable after progressively broader feedback and testing.
Dev became Chrome's fast public development channel, historically receiving builds about weekly and giving Google field feedback before code advanced to Beta and Stable.
Google now positions Dev for developers and IT staff who want a substantially earlier view of browser and web-platform changes. Current macOS channel builds use separate identities and profiles, making parallel testing practical.
Use Dev to test sites, extensions, policies, and applications against browser changes well before they reach Stable. Google warns that it remains subject to bugs despite receiving testing.
The current macOS build has a Dev-specific Application Support directory, keeping its browser profile separate from other Chrome channels.
Dev is the middle ground for browser-channel enthusiasts: closer to active development than Beta, but subjected to more testing than Canary. Package managers make it simple to retain this distinct rung of the browser release pipeline alongside safer installations.
Sicherheitslage
Für google-chrome@dev 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 DevExecutables
| 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/dev/
Installationsmetadaten
| Paketschlüssel | cask:google-chrome@dev |
|---|---|
| Version | 160.0.8171.0 |
| Paketmanager | Homebrew Cask |
| Paketmanager-Seite | https://formulae.brew.sh/cask/google-chrome@dev |
| Homepage | https://www.google.com/chrome/dev/ |
| Upstream-Dokumentation | https://www.google.com/chrome/dev/ |
| Quellarchiv | https://dl.google.com/chrome/mac/universal/dev/googlechromedev.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@dev |
| 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.