agent safety

Agent safety answer

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

Credential access

Reads Cloudflare tokens, account IDs, project config, and environment variables.

Remote mutation

Can deploy workers, change routes, and mutate Cloudflare resources.

Publish/artifact risk

Publishes worker scripts and static assets to production edges.

Recommended control

Gate deploy, secret, route, and account mutation commands.

Agent-use guidance

Allow local build/dev; require approval before deploys, secret changes, or route updates.

install

Additional install commands

macOS

Homebrewverified · 100%

brew install cloudflare-wrangler

local Homebrew formula metadata

MacPortsverified · 94%

sudo port install wrangler

MacPorts ports tree · devel/wrangler/Portfile · source: api.github.com

Linux

Nixverified · 92%

nix profile install nixpkgs#wrangler

nixpkgs package indexes · pkgs/by-name/wr/wrangler/package.nix · source: api.github.com

Arch Linux pacmanverified · 92%

sudo pacman -S wrangler

Arch Linux sync databases · wrangler · source: geo.mirror.pkgbuild.com

overview

Package summary

CLI tool for Cloudflare Workers

Project links

Commands and aliases

wrangler
wrangler2

history

Project history and usage

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.

Project history

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.

Adoption history

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.

How it is used

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.

Why package nerds care

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.

Timeline

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

security posture

Risk level: orange

infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

infrastructure mutation or orchestration signal

Signals

text:cloud

Install behavior

No Homebrew post-install hook is recorded in formula metadata.
Homebrew bottle metadata is available for 6 platform targets.
Installs with 1 runtime dependencies.

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/Preferences/.wrangler/config/default.toml
Unix: ~/.wrangler/config/default.toml~/.config/.wrangler/config/default.toml$XDG_CONFIG_HOME/.wrangler/config/default.toml

Credential files

Credential-bearing paths to review before unattended agent runs.

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

executables

Installed executables

Command	Kind	Exposure	Note
`wrangler`	cli	global executable
`wrangler2`	cli	global executable

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-07-08

manager version4.107.0

manager updated2026-07-03

local dataok

upstreamnot checked

latest detectednot detected

https://developers.cloudflare.com/workers/

infoRelease/tag comparison is only available for GitHub repositories.https://developers.cloudflare.com/workers/none confidence

install metadata

Package metadata

Package key	brew:cloudflare-wrangler
Version	4.107.0
Package manager	Homebrew
Package manager page	https://formulae.brew.sh/formula/cloudflare-wrangler
Homepage	https://developers.cloudflare.com/workers/
Repository	https://github.com/cloudflare/workers-sdk
Upstream docs	https://developers.cloudflare.com/workers/wrangler
License	Apache-2.0 OR MIT
Source archive	https://registry.npmjs.org/wrangler/-/wrangler-4.107.0.tgz
Last updated	2026-07-03T17:51:07Z
Pulse	updated
Dependencies	node
Bottle	available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-install	not defined
Service	none declared

registry facts

Source database details

Source Database	Homebrew formula API
Tap	homebrew/core
Full Name	cloudflare-wrangler
Version Scheme	0
Revision	0
Bottle Stable Root URL	https://ghcr.io/v2/homebrew/core
Deprecated	no
Disabled	no
Keg Only	no
URL Keys	stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

MacPorts94%

wrangler

sudo port install wrangler

installed executable or alias match
Matched by: Wrangler

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

Nix92%

wrangler

nix profile install nixpkgs#wrangler

installed executable or alias match
Matched by: Wrangler

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

pacman92%

wrangler 4.82.2-1

The CLI for Cloudflare Workers

https://github.com/cloudflare/workers-sdk

sudo pacman -S wrangler

License: Apache-2.0 AND MIT
Architecture: x86_64
5 dependencies
installed executable or alias match
Matched by: Wrangler

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

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

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.

Combined YAML source

View the package source record on GitHub.

combined/cloudflare-wrangler.yml

Used sources

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

Install cloudflare-wrangler with Homebrew, MacPorts, Nix, pacman