Automic VaultAutomic Vault

brew

Install moto with Homebrew

Mock AWS services. Version 5.2.2 via Homebrew; verified 2026-06-21.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install moto

local Homebrew formula metadata

overview

Package summary

Mock AWS services

Commands and aliases

  • moto_proxy
  • moto_server

history

Project history and usage

Moto began as Steve Pulec's Python library for mocking AWS services, with the project AUTHORS file naming Pulec as the original writer and a long contributor list behind the broader emulator. Its role is tightly coupled to the boto and boto3 ecosystem: tests wrap AWS-using code with Moto's mocks so that S3, DynamoDB, IAM, Lambda, and other service calls are handled locally instead of reaching a real AWS account.

Project history

The project became a standard testing tool because it supports both in-process Python decorators/context managers and a stand-alone HTTP server mode. The server mode lets non-Python SDKs point at Moto's fake AWS endpoints, while the Python API fits normal unit-test and pytest workflows. Moto 5.0.0 marked a major API simplification by replacing service-specific decorators with a single `mock_aws` decorator and making one MotoServer instance the recommended server shape, a milestone aimed at simplifying usage and state management.

How it is used

As a package-manager entry, Moto is more of a developer-test dependency than an end-user CLI, although Homebrew exposes `moto_server` and `moto_proxy` executables for local service emulation. Its closest neighbors are broader local cloud emulators and hand-written mocks, but Moto's niche is AWS-specific behavioral coverage that can be pulled directly into Python tests.

security posture

Risk level: orange

formula declares a Homebrew service.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • formula declares a Homebrew service

Signals

  • metadata:service

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Formula metadata declares a service or daemon block.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Installs with 6 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.

executables

Installed executables

CommandKindExposureNote
moto_proxycliglobal executable
moto_servercliglobal 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 version5.2.2
manager updated2026-06-21
local dataok
upstreamnot checked
latest detectednot detected

http://getmoto.org/

  • infoRelease/tag comparison is only available for GitHub repositories.http://getmoto.org/none confidence

install metadata

Package metadata

Package keybrew:moto
Version5.2.2
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/moto
Homepagehttp://getmoto.org/
Repositoryhttps://github.com/getmoto/moto
Upstream docshttps://docs.getmoto.org/
LicenseApache-2.0
Source archivehttps://files.pythonhosted.org/packages/47/63/d944f387582cc53f53febbff2b3fa36a6d2ed7c1feef8990bf646cfa9cba/moto-5.2.2.tar.gz
Last updated2026-06-21T10:54:20Z
Pulseupdated
Dependenciescertifi, cryptography, libyaml, pydantic, python@3.14, rpds-py
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicedeclared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namemoto
Version Scheme0
Revision1
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

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

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment