pkg.soopen package index

cask

Install google-chrome@dev with Homebrew Cask

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

install

Additional install commands

macOS

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

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 Dev is Google's fast-moving developer preview channel, intended to expose current browser work earlier than Beta while receiving more testing than Canary.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

  • 2008: Google launched Chrome and Chromium.
  • 2008: The Chrome release blog documented Dev as a distinct channel when Chrome 1.0 became Stable.

Related projects

  • Google Chrome Stable
  • Google Chrome Beta
  • Google Chrome Canary
  • Chromium
  • Chrome for Testing

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for google-chrome@dev. 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 Dev

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.8171.0
manager updated
local dataok
upstreamnot checked
latest detectednot detected

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

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

install metadata

Package metadata

Package keycask:google-chrome@dev
Version160.0.8171.0
Package managerHomebrew Cask
Package manager pagehttps://formulae.brew.sh/cask/google-chrome@dev
Homepagehttps://www.google.com/chrome/dev/
Upstream docshttps://www.google.com/chrome/dev/
Source archivehttps://dl.google.com/chrome/mac/universal/dev/googlechromedev.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@dev
Names
  • Google Chrome Dev
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