pkg.soopen package index

brew / Rang 2851

aws-amplify mit Homebrew, scoop installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für aws-amplify in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install aws-amplify

local Homebrew formula metadata

Windows

Scoopverifiziert · 92%
scoop install main/aws-amplify

Scoop official bucket manifest trees · bucket/aws-amplify.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Build full-stack web and mobile apps in hours. Easy to start, easy to scale

Befehle und Aliase

  • amplify

Verlauf

Projektgeschichte und Nutzung

AWS Amplify CLI is the command-line toolchain for creating, integrating, and managing AWS-backed web and mobile app services. The Homebrew package installs the amplify command, historically centered on Amplify Gen 1 workflows such as amplify init, add, push, pull, and env management.

Projektgeschichte

AWS announced the AWS Amplify library and AWS Mobile CLI in 2017, and that announcement now carries an editorial note directing users to the AWS Amplify CLI. In August 2018, AWS announced the Amplify CLI toolchain as the newer workflow for configuring local project state and deploying cloud resources.

The Amplify CLI's Gen 1 architecture used AWS CloudFormation and nested stacks so developers could add or modify backend configurations locally before pushing them to an AWS account. Its file layout grew around an amplify/ project directory containing backend state, team environment metadata, feature flags, and generated client configuration.

Amplify later introduced Gen 2, a code-first TypeScript backend experience built on AWS CDK constructs. AWS made Amplify Gen 2 generally available on May 6, 2024, which shifted new projects toward ampx and file-based TypeScript backend definitions while leaving Gen 1 CLI documentation in maintenance mode.

Adoptionsgeschichte

Amplify CLI was adopted heavily by frontend and mobile developers who wanted AWS-backed auth, APIs, storage, functions, and hosting without hand-writing all of the CloudFormation. Its category model let users add Cognito, AppSync, S3, Lambda, and hosting resources from prompts and then commit the resulting project files.

The tool also became a source of package-manager friction because it is an npm-distributed CLI with a large plugin ecosystem, but many users want it installed like any other system command. Homebrew and Scoop formulas serve that audience by making amplify available outside a per-project node_modules tree.

Wie es verwendet wird

In Gen 1 workflows, users run amplify configure to connect local tooling to an AWS account, amplify init to create an Amplify project, amplify add <category> to model backend resources, and amplify push to deploy generated CloudFormation. The CLI writes project state under amplify/ and consumes AWS shared config and credentials files for account access.

Amplify's documented project files include amplify/.config/, backend-config.json under both amplify/backend and amplify/#current-cloud-backend, team-provider-info.json, cli.json, category cli-inputs.json files, generated client configuration, and deployment secrets stored outside the repository. Gen 2 workflows instead use npx ampx commands and generate amplify_outputs.json for client configuration.

Warum Paket-Nerds sich dafür interessieren

For package nerds, aws-amplify is a case study in packaging a fast-moving JavaScript cloud CLI as a system formula. It has to bridge npm expectations, Node version support, AWS credentials, generated project files, and the fact that the product line split between Gen 1 CLI and Gen 2 ampx workflows.

It is also historically useful because old Amplify projects often encode their backend state in generated JSON files. Having a reproducible CLI installation can be the difference between being able to pull, inspect, migrate, or retire an older Amplify backend.

Zeitleiste

  • 2017: AWS announced AWS Amplify and the AWS Mobile CLI, with later guidance to use Amplify CLI going forward.
  • 2018: AWS announced the AWS Amplify CLI toolchain.
  • 2021: AWS Amplify CLI added support for function environment variables and secrets.
  • 2024: AWS Amplify Gen 2 became generally available as a fullstack TypeScript experience.
  • 2027: AWS Amplify Gen 1 documentation says Gen 1 reaches end of life on May 1, 2027.

Related projects

  • AWS Amplify Gen 2 backend tooling uses the @aws-amplify/backend-cli package and ampx commands.
  • AWS CDK underpins Amplify Gen 2's backend-building model and can be used for custom resources.
  • AWS CloudFormation is the deployment substrate used by the Gen 1 CLI and nested-stack architecture.

Quellen

Sicherheitslage

Noch keine Protected-Tool-Abdeckung gefunden

Für aws-amplify wurde kein passendes lokales Secret-Handling-Manifest gefunden. Nucleus-Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.

Installationsverhalten

  • Es wurden keine Homebrew-Bottle-Metadaten erfasst.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

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
amplify/.config/amplify/backend/backend-config.jsonamplify/#current-cloud-backend/backend-config.jsonamplify/team-provider-info.jsonamplify/cli.jsonamplify/**/cli-inputs.json~/.aws/amplify/deployment-secrets.json

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.aws/credentials
Windows
%USERPROFILE%\.aws\credentials

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
amplifyExecutableindexiertes ExecutableAus dem lokalen Executable-Index erkannt.

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-08-03
Manager-Version14.5.1
Manager aktualisiert2026-06-26
lokale Datenunbekannt
Upstreamnicht verfügbar
neueste erkannte Versionnicht erkannt
  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:aws-amplify
Version14.5.1
PaketmanagerHomebrew
Homepagehttps://aws.amazon.com/amplify/
Zuletzt aktualisiert2026-06-26T15:54:25Z
Pulseupdated
Bottlenicht erfasst
Dienstkeiner deklariert

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Scoop95%

main/aws-amplify

scoop install main/aws-amplify
  • normalized package name match
  • Abgeglichen nach: Aws Amplify
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/aws-amplify.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

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