macOS
brew install bowerlocal Homebrew formula metadata
brew
Package manager for the web. Version 1.8.14 via Homebrew; verified from local package data.
install
brew install bowerlocal Homebrew formula metadata
sudo apk add bowerAlpine Linux edge package indexes · bower · source: dl-cdn.alpinelinux.org
sudo pacman -S bowerArch Linux sync databases · bower · source: geo.mirror.pkgbuild.com
choco install bowerChocolatey community package catalog · bower · source: community.chocolatey.org
overview
Package manager for the web
history
Bower was one of the defining front-end package managers of the early 2010s: a Git-backed, browser-asset-oriented tool built before npm, Yarn, webpack, Vite, and modern bundlers absorbed most client-side dependency management.
The official About page says Bower was created at Twitter by @fat and @maccman and released as part of Twitter's open source effort in 2012. The public GitHub repository was created in September 2012 and describes the project as a package manager for the web.
Bower's design targeted front-end assets rather than Node modules. The README and homepage emphasize a generic, unopinionated solution, no shared system-wide dependencies, a flat dependency tree, Git-based package resolution, and package-agnostic components containing JavaScript, CSS, fonts, images, or other web assets.
Bower became widely used by front-end projects that wanted predictable browser dependency installation before the npm ecosystem fully embraced front-end packages. Its registry, `bower.json`, `.bowerrc`, and `bower_components/` directory became common project artifacts.
By 2017, the official Bower site and blog were already recommending Yarn and build tools for new front-end projects. The migration blog explains that Yarn 1.x could install many Bower packages but not resolve Bower dependencies directly, leading to compatibility helpers such as `bower-away` for legacy projects.
Users installed Bower globally with npm, then ran commands such as `bower install`, `bower search`, `bower info`, `bower update`, and `bower register`. Dependencies were recorded in `bower.json`, installed into `bower_components/`, and controlled with `.bowerrc` settings.
Bower intentionally did not concatenate, minify, or bundle code; it installed the requested versions and left integration to tools such as Grunt, gulp, RequireJS, webpack, or later build systems.
Bower matters because it captures a transitional moment in JavaScript packaging: browser packages still often lived as Git repositories with dist files, npm was not yet the universal front-end registry, and flat dependency graphs looked attractive for avoiding duplicate browser payloads.
Its decline is equally instructive. The official recommendation to use Yarn and bundlers for new projects marks the shift from asset-package managers toward npm-centered dependency graphs, lockfiles, checksums, and integrated build pipelines.
security posture
infrastructure mutation or orchestration signal.
orange risk · medium confidence · infrastructure
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
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.
.bowerrc~/.bowerrc/.bowerrcexecutables
| Command | Kind | Exposure | Note |
|---|---|---|---|
bower | cli | global executable |
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.
install metadata
| Package key | brew:bower |
|---|---|
| Version | 1.8.14 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/bower |
| Homepage | https://bower.io/ |
| Repository | https://github.com/bower/bower |
| Upstream docs | https://bower.io/docs/api |
| License | MIT |
| Source archive | https://registry.npmjs.org/bower/-/bower-1.8.14.tgz |
| Dependencies | node |
| Bottle | available (on arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, monterey, sonoma, ventura, x86_64_linux) |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | bower |
| Version Scheme | 0 |
| Revision | 0 |
| Conflicts With |
|
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
bower 1.1.1-r1
curses frontend for the Notmuch email system
https://github.com/wangp/bower
sudo apk add bowerbower-doc 1.1.1-r1
curses frontend for the Notmuch email system (documentation)
https://github.com/wangp/bower
sudo apk add bower-docbower 1.8.14-3
A package manager for the web
sudo pacman -S bowerbower
choco install bowersource trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.