# Installer cloudflare-wrangler avec Homebrew, MacPorts, Nix, pacman

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

## installation

```sh
sudo av install brew:cloudflare-wrangler
```

## Réponse sur la sécurité des agents

cloudflare-wrangler deploys and manages Cloudflare Workers and related resources.

- **Accès aux identifiants:** Reads Cloudflare tokens, account IDs, project config, and environment variables.
- **Modification distante:** Can deploy workers, change routes, and mutate Cloudflare resources.
- **Risque de publication ou d'artéfact:** Publishes worker scripts and static assets to production edges.
- **Contrôle recommandé:** Gate deploy, secret, route, and account mutation commands.
- **Conseils d'utilisation par les agents:** Allow local build/dev; require approval before deploys, secret changes, or route updates.

Commandes d'installation supplémentaires:

### macOS

- Homebrew (100%):

```sh
brew install cloudflare-wrangler
```

  Preuve: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install wrangler
```

  Preuve: MacPorts ports tree: devel/wrangler/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#wrangler
```

  Preuve: nixpkgs package indexes: pkgs/by-name/wr/wrangler/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- pacman (92%):

```sh
sudo pacman -S wrangler
```

  Preuve: Arch Linux sync databases: wrangler from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

## Faits du paquet

- **Clé du paquet:** brew:cloudflare-wrangler
- **Gestionnaire de paquets:** Homebrew
- **Version:** 4.118.0
- **Résumé source:** CLI tool for Cloudflare Workers
- **Page d'accueil:** <https://developers.cloudflare.com/workers/>
- **Dernière mise à jour:** 2026-08-01T15:07:28Z
- **Généré:** 2026-08-03T19:37:03+00:00

## exécutables

- wrangler (alias)
- wrangler2 (alias)

## Comportement d'installation

- Bouteille: non disponible

## Version et fraîcheur

- page générée: 2026-08-03
- version du gestionnaire: 4.118.0
## Historique du projet et usages

Wrangler is Cloudflare's command-line interface for building, previewing, configuring, and deploying Cloudflare Workers and related developer-platform resources. The modern package lives in the official Cloudflare Workers SDK monorepo, while the earlier Wrangler v1 repository is archived as wrangler-legacy.

### Historique du projet

Cloudflare introduced Wrangler as a Workers-focused CLI during the early growth of Workers as an edge/serverless platform. The original public Wrangler repository was created in 2019 and later archived as the v1 codebase, with current development consolidated into the workers-sdk monorepo that Cloudflare describes as home to Wrangler.

The move into workers-sdk matched Wrangler's broadening role: it stopped being only a deploy command for Worker scripts and became the CLI surface for local development, configuration files, environments, asset workflows, and other Cloudflare developer-platform features.

### Historique d'adoption

Official Cloudflare documentation presents Wrangler as the standard CLI for Workers development. Package-manager metadata in this batch shows the Homebrew formula alongside MacPorts, Nix, and Arch packaging, while Cloudflare's primary installation path remains the JavaScript package ecosystem.

GitHub release metadata shows the workers-sdk monorepo publishing frequent wrangler-tagged releases through 2026, which is a useful signal for maintainers because the Homebrew package tracks a fast-moving upstream CLI rather than a slow system utility.

### Modes d'utilisation

Developers use Wrangler to scaffold and configure Workers projects, run local development, deploy Workers, manage bindings and environments, and interact with Cloudflare platform resources from scripts and CI.

Wrangler configuration is project-local in wrangler.jsonc, wrangler.json, or wrangler.toml. Environment variables and secrets can be loaded from .env-style files for local workflows, with production secrets managed through Cloudflare's documented secret mechanisms.

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

Wrangler is interesting to package maintainers because it is a Node-based, vendor-owned cloud CLI distributed both through npm-style workflows and operating-system package managers. That creates the usual tension between fast upstream release cadence, lockfile-heavy JavaScript packaging, and distro expectations for reproducibility.

The Homebrew formula name cloudflare-wrangler also preserves a vendor-qualified package identity even though the executable is wrangler, which helps avoid namespace ambiguity with unrelated tools.

### Chronologie

- 2019: Original Cloudflare Wrangler v1 repository was created and Wrangler became the Workers CLI.
- 2021: Cloudflare created the workers-sdk monorepo, now described as the home of Wrangler.
- 2022: Early wrangler-tagged releases appeared in workers-sdk as the modern CLI line developed.
- 2023: Wrangler v1 repository was archived after v1 maintenance ended.
- 2026: workers-sdk continued publishing frequent wrangler@4.x releases.

### Related projects

- Cloudflare Workers is the runtime and deployment target Wrangler primarily manages.
- workers-sdk is the official monorepo that contains Wrangler and adjacent Workers developer tooling.
- Miniflare and workerd are related pieces of the local/runtime tooling stack around Workers development.

### Sources

- <https://developers.cloudflare.com/workers/wrangler/>
- <https://developers.cloudflare.com/workers/wrangler/configuration/>
- <https://github.com/cloudflare/workers-sdk>
- <https://github.com/cloudflare/wrangler-legacy>


## Notes de sécurité

infrastructure mutation or orchestration signal.

- **Risque Geiger:** orange / moyen
- infrastructure mutation or orchestration signal


## 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

- macOS: ~/Library/Preferences/.wrangler/config/default.toml
- Unix: ~/.wrangler/config/default.toml, ~/.config/.wrangler/config/default.toml, $XDG_CONFIG_HOME/.wrangler/config/default.toml

## Credential files

- macOS: ~/Library/Preferences/.wrangler/config/default.toml
- Unix: ~/.wrangler/config/default.toml, ~/.config/.wrangler/config/default.toml, $XDG_CONFIG_HOME/.wrangler/config/default.toml
## Autres enregistrements de gestionnaires de paquets

- MacPorts - wrangler: installed executable or alias match | MacPorts ports tree: devel/wrangler/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
- Nix - wrangler: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/wr/wrangler/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- pacman - wrangler - 4.111.0-1: installed executable or alias match | Arch Linux sync databases: wrangler from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | The CLI for Cloudflare Workers | https://github.com/cloudflare/workers-sdk


## Combined YAML source

View the package source record on GitHub. [combined/cloudflare-wrangler.yml](https://github.com/mxcl/pkgdb/blob/main/combined/cloudflare-wrangler.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph
- curated agent safety answer