npmpackage.info

Gathering detailed insights and metrics for @aws-amplify/amplify-cli-core

Other packages similar to @aws-amplify/amplify-cli-core

amplify-cli-core

4.0.4

Amplify CLI Core

@aws-amplify/cli-core

2.1.1

Contains common CLI functionality like logging and prompting. This package is used by both cli and create-amplify to provide a normalized CLI experience

Gathering detailed insights and metrics for @aws-amplify/amplify-cli-core

@aws-amplify/amplify-cli-core - 4.4.2 | npmpackage.info

@aws-amplify/amplify-cli-core

The AWS Amplify CLI is a toolchain for simplifying serverless web and mobile development.

4.4.2

2,837

Apache-2.0

TypeScript

799.45 kB

5.8

Installations

npm install @aws-amplify/amplify-cli-core

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Node Version

22.12.0

NPM Version

lerna/8.2.1/node@v22.12.0+x64 (linux)

Pull Requests

Open

57

Total

5,894

Closed

894

Merged

4,943

Issues

Open

674

Total

6,779

Closed

6,105

Releases

190

14.0.0

v14.0.0

Updated on Jul 01, 2025

13.0.1

v13.0.1

Updated on Apr 17, 2025

13.0.0

v13.0.0

Updated on Feb 25, 2025

12.14.4

v12.14.4

Updated on Feb 20, 2025

12.14.3

v12.14.3

Updated on Feb 07, 2025

12.14.2

v12.14.2

Updated on Jan 30, 2025

View All 190 releases

Languages

TypeScript

JavaScript

EJS

Shell

Swift

Python

Yacc

Lex

CSS

Java

HTML

Makefile

Dockerfile

Dart

Ruby

TypeScript (80.39%)

JavaScript (14.56%)

EJS (2.79%)

Shell (0.93%)

Swift (0.76%)

Python (0.15%)

Yacc (0.11%)

Lex (0.09%)

CSS (0.07%)

Go (0.05%)

Java (0.05%)

HTML (0.04%)

Makefile (0.01%)

Dockerfile (0.01%)

Developer

aws-amplify

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

Apache-2.0 License

2,837 Stars

6,904 Commits

821 Forks

128 Watchers

867 Branches

338 Contributors

Updated on Jul 13, 2025

Maintainers

View All 338 Contributors

Package Meta Information

Latest Version

4.4.2

Package Id

@aws-amplify/amplify-cli-core@4.4.2

Unpacked Size

799.45 kB

Size

153.66 kB

File Count

363

NPM Version

lerna/8.2.1/node@v22.12.0+x64 (linux)

Node Version

22.12.0

Published on

Jul 01, 2025

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Reporting Bugs/Feature Requests

[!Important]

Amplify Gen 2 is now generally available

If you are starting a new project, we recommend starting with Amplify Gen 2.

If you are an existing Gen 1 customer, we recommend that you continue working with your Gen 1 Amplify project. We are actively developing migration tooling to aid in transitioning your project from Gen 1 to Gen 2. We remain committed to supporting both Gen 1 and Gen 2 for the foreseeable future.

Customers on Gen 1 will continue to receive support for high-priority bugs and essential security updates.

AWS Amplify CLI (Gen 1)

The AWS Amplify CLI is a toolchain which includes a robust feature set for simplifying mobile and web application development. The CLI uses AWS CloudFormation and nested stacks to allow you to add or modify configurations locally before you push them for execution in your account.

Install the CLI
Commands Summary
Tutorials
Contributing
Start building your app
Changelog

Install the CLI

Requires Node.js® version 22 or later

Install and configure the Amplify CLI as follows:

1$ npm install -g @aws-amplify/cli
2$ amplify configure

Commands Summary

The Amplify CLI supports the commands shown in the following table.

Command	Description
amplify configure	Configures the AWS access credentials, AWS Region and sets up a new AWS User Profile
amplify init	Initializes a new project, sets up deployment resources in the cloud and prepares your project for Amplify.
amplify configure project	Updates configuration settings used to setup the project during the init step.
amplify add `<category>`	Adds cloud features to your app.
amplify update `<category>`	Updates existing cloud features in your app.
amplify push [--no-gql-override]	Provisions cloud resources with the latest local developments. The 'no-gql-override' flag does not automatically compile your annotated GraphQL schema and will override your local AppSync resolvers and templates.
amplify pull	Fetch upstream backend environment definition changes from the cloud and updates the local environment to match that definition.
amplify publish	Runs `amplify push`, publishes a static assets to Amazon S3 and Amazon CloudFront (*hosting category is required).
amplify status [ `<category>`...]	Displays the state of local resources that haven't been pushed to the cloud (Create/Update/Delete).
amplify status -v [ `<category>`...]	Verbose mode - Shows the detailed verbose diff between local and deployed resources, including cloudformation-diff
amplify serve	Runs `amplify push`, and then executes the project's start command to test run the client-side application.
amplify delete	Deletes resources tied to the project.
amplify help \| amplify `<category>` help	Displays help for the core CLI.
amplify codegen add \| generate	Performs generation of strongly typed objects using a GraphQL schema.
amplify env add \| list \| remove \| get \| pull \| import \| checkout	See the multienv docs.

Category specific commands:

Tutorials

Developing

To set up your local development environment, go to Local Environment Setup.

To test your category, do the following:

1cd <your-test-front-end-project>
2amplify-dev init
3amplify-dev <your-category> <subcommand>

Before pushing code or sending a pull request, do the following:

At the command line, run yarn lint at the top-level directory. This invokes eslint to check for lint errors in all of our packages.
You can use yarn lint to find some of the lint errors. To attempt fix them, go to the package that has errors and run yarn lint-fix
If there are any remaining lint errors, resolve them manually. Linting your code is a best practice that ensures good code quality so it's important that you don't skip this step.

Contributing

We are thankful for any contributions from the community. Look at our Contribution Guidelines.

No vulnerabilities found.

10

Maintained

Determines if the project is "actively maintained".

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

10

License

Determines if the project has defined a license.

10

Security-Policy

Determines if the project has published a security policy.

10

SAST

Determines if the project uses static code analysis.

9

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

3

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Signed-Releases

Determines if the project cryptographically signs release artifacts.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 0

Details

Warn: third-party GitHubAction not pinned by hash: .github/workflows/closed-issue-message.yml:9: update your workflow using https://app.stepsecurity.io/secureworkflow/aws-amplify/amplify-cli/closed-issue-message.yml/dev?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-tests.yaml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/aws-amplify/amplify-cli/codeql-tests.yaml/dev?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-tests.yaml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/aws-amplify/amplify-cli/codeql-tests.yaml/dev?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql-tests.yaml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/aws-amplify/amplify-cli/codeql-tests.yaml/dev?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yaml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/aws-amplify/amplify-cli/codeql.yaml/dev?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yaml:30: update your workflow using https://app.stepsecurity.io/secureworkflow/aws-amplify/amplify-cli/codeql.yaml/dev?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/codeql.yaml:36: update your workflow using https://app.stepsecurity.io/secureworkflow/aws-amplify/amplify-cli/codeql.yaml/dev?enable=pin
Warn: third-party GitHubAction not pinned by hash: .github/workflows/issue-pending-response.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/aws-amplify/amplify-cli/issue-pending-response.yml/dev?enable=pin
Warn: containerImage not pinned by hash: packages/amplify-container-hosting/resources/express-template/Dockerfile:1: pin your Docker image by updating public.ecr.aws/bitnami/node:14-prod-debian-10 to public.ecr.aws/bitnami/node:14-prod-debian-10@sha256:a494ad32bfa356b808d167e744ce69810401b4e8b38421f05d049af8ea01d457
Warn: containerImage not pinned by hash: packages/amplify-container-hosting/resources/simple-template/Dockerfile:2
Warn: containerImage not pinned by hash: packages/amplify-container-hosting/resources/simple-template/Dockerfile:9: pin your Docker image by updating public.ecr.aws/nginx/nginx:1 to public.ecr.aws/nginx/nginx:1@sha256:839c5f5ff4e05085af6418056c20655f7c7c9a7d7651911cc3deeaa72eb34b81
Warn: npmCommand not pinned by hash: packages/amplify-container-hosting/resources/express-template/Dockerfile:6
Warn: npmCommand not pinned by hash: shared-scripts.sh:514
Warn: npmCommand not pinned by hash: shared-scripts.sh:515
Warn: npmCommand not pinned by hash: shared-scripts.sh:524
Warn: npmCommand not pinned by hash: shared-scripts.sh:671
Warn: npmCommand not pinned by hash: shared-scripts.sh:672
Warn: downloadThenRun not pinned by hash: shared-scripts.sh:707
Info: 5 out of 11 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 2 third-party GitHubAction dependencies pinned
Info: 0 out of 3 containerImage dependencies pinned
Info: 0 out of 6 npmCommand dependencies pinned
Info: 0 out of 1 downloadThenRun dependencies pinned

0

Fuzzing

Determines if the project uses fuzzing.

Score

5.8

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More

Other packages similar to @aws-amplify/amplify-cli-core

Other packages similar to @aws-amplify/amplify-cli-core

@aws-amplify/amplify-cli-core

Installations

Developer Guide

Yes

CommonJS

22.12.0

lerna/8.2.1/node@v22.12.0+x64 (linux)

Pull Requests

57

5,894

894

4,943

Issues

674

6,779

6,105

Releases

Languages

Developer

aws-amplify

Download Statistics

GitHub Statistics

Maintainers

Package Meta Information

Total Downloads

NaN

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

Dev Dependencies

Reporting Bugs/Feature Requests

Amplify Gen 2 is now generally available

AWS Amplify CLI (Gen 1)

Install the CLI

Commands Summary

Category specific commands:

Tutorials

Developing

Contributing

10

10

10

10

10

10

9

3

0

0

0

0

0

5.8

/10