Automic VaultAutomic Vault

brew

Installer bower avec Homebrew, apk, chocolatey, pacman

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de bower pour les workflows d'agents IA.

Commande d'installationNotes de sécurité

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install bower

local Homebrew formula metadata

aperçu

Résumé du paquet

Package manager for the web

Commandes et alias

  • bower

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

  • 2012: Created at Twitter and released as part of Twitter's open source effort.
  • 2012: Public GitHub repository created.
  • 2014: GitHub Releases include the 1.x release line.
  • 2017: Official Bower blog published migration guidance away from Bower.
  • 2020s: Maintained mainly for legacy projects while the site recommends Yarn and modern build tools for new work.

Related projects

  • npm is the package manager whose registry and package format eventually absorbed much front-end package distribution.
  • Yarn is the replacement recommended by the official Bower site for many new or migrated front-end projects.
  • webpack, Vite, Parcel, Grunt, gulp, and RequireJS are related build or module tools that either complemented Bower or replaced the workflow around it.

posture de sécurité

Niveau de risque : orange

infrastructure mutation or orchestration signal.

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

  • infrastructure mutation or orchestration signal

Signaux

  • text:package manager

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 10 plateformes.
  • S’installe avec 1 dépendances d’exécution.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des 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.

Unix
.bowerrc~/.bowerrc/.bowerrc

exécutables

Exécutables installés

CommandeTypeExpositionNote
bowercliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-25
version du gestionnaire1.8.14
gestionnaire mis à jour
données localesOK
amontnot checked
dernière version détectéenon détecté

https://bower.io/

  • infoNo package-manager update timestamp was available.confiance faible
  • infoRelease/tag comparison is only available for GitHub repositories.https://bower.io/confiance none

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:bower
Version1.8.14
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/bower
Page d'accueilhttps://bower.io/
Dépôthttps://github.com/bower/bower
Docs amonthttps://bower.io/docs/api
LicenceMIT
Archive sourcehttps://registry.npmjs.org/bower/-/bower-1.8.14.tgz
Dépendancesnode
Bouteilledisponible (sur arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, monterey, sonoma, ventura, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namebower
Version Scheme0
Revision0
Conflicts With
  • bower-mail
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

apk95%

bower 1.1.1-r1

curses frontend for the Notmuch email system

https://github.com/wangp/bower

sudo apk add bower
  • License: GPL-3.0-or-later
  • Architecture: x86_64
  • Source Package: bower
  • 1 Dépendances
  • 1 fournit
  • normalized package name match
  • Correspondance par : Bower
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: bower from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
apk95%

bower-doc 1.1.1-r1

curses frontend for the Notmuch email system (documentation)

https://github.com/wangp/bower

sudo apk add bower-doc
  • License: GPL-3.0-or-later
  • Architecture: x86_64
  • Source Package: bower
  • normalized package name match
  • Correspondance par : Bower
Alpine Linux edge package indexes · dl-cdn.alpinelinux.org · Alpine Linux edge package indexes: bower-doc from https://dl-cdn.alpinelinux.org/alpine/edge/community/x86_64/APKINDEX.tar.gz
pacman95%

bower 1.8.14-3

A package manager for the web

https://bower.io/

sudo pacman -S bower
  • License: MIT
  • Architecture: any
  • 3 Dépendances
  • normalized package name match
  • Correspondance par : Bower
Arch Linux sync databases · geo.mirror.pkgbuild.com · Arch Linux sync databases: bower from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz
Chocolatey95%

bower

choco install bower
  • normalized package name match
  • Correspondance par : Bower
Chocolatey community package catalog · community.chocolatey.org · Chocolatey community package catalog: bower from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='9.1916','tektoncd-cli'

graphe de paquets

Les liens viennent du graphe local de relations entre paquets, des suppléments, des dépendances, des correspondances d'écosystèmes et de l'appartenance aux hubs.

Outils liés

  • nodeRuntime dependency declared by Homebrew.
  • pulpPopular package that depends on this formula.

Même workflow

  • opamShares av.db curated category or tags: cli, developer-tools, package-manager, package-managers.
  • soarShares av.db curated category or tags: cli, developer-tools, package-manager, package-managers.
  • aubeShares av.db curated category or tags: cli, developer-tools, javascript, package-manager.
  • eleventyShares av.db curated category or tags: cli, developer-tools, javascript, web.
  • pnpmShares av.db curated category or tags: cli, developer-tools, javascript, package-manager.
  • spagoShares av.db curated category or tags: cli, developer-tools, javascript, package-manager.
  • bowerSame normalized package name in another local ecosystem.

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment