@aws-amplify/amplify-category-custom

v3.1.18

amplify-cli custom resources plugin For more information about how to use this package see README

Latest version published 18 hours ago

License: Apache-2.0

NPM

GitHub

Package Health Score

89 / 100

security
Security review needed
popularity
Popular
maintenance
Healthy
community
Active

Explore Similar Packages

Security

Security review needed

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
3.1.18	\|	04/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.0.9	\|	06/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.6.6	\|	02/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.5.5	\|	11/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
2.3.7	\|	12/2021	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

Apache-2.0

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Popular

Weekly Downloads (67,135)

GitHub Stars: 2.78K
Forks: 810
Contributors: 270

Direct Usage Popularity

The npm package @aws-amplify/amplify-category-custom receives a total of 67,135 downloads a week. As such, we scored @aws-amplify/amplify-category-custom popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @aws-amplify/amplify-category-custom, we found that it has been starred 2,783 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Active

Readme.md: Yes
Contributing.md: Yes
Code of Conduct: Yes
Contributors: 270
Funding: No

A good and healthy external contribution signal for @aws-amplify/amplify-category-custom project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

Maintenance

Healthy

Commit Frequency

Open Issues: 665
Open PR: 50
Last Release: 18 hours ago
Last Commit: 20 days ago

Further analysis of the maintenance status of @aws-amplify/amplify-category-custom based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @aws-amplify/amplify-category-custom demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: not defined

Age: 2 years
Dependencies: 8 Direct
Versions: 405
Install Size: 135 kB
Dist-tags: 141
# of Files: 63
Maintainers: 9
TS Typings: No

@aws-amplify/amplify-category-custom has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Readme

Reporting Bugs/Feature Requests

> [!TIP]
> Preview: AWS Amplify's new code-first DX (Gen 2) for building backends > > The next generation of Amplify's backend building experience with a TypeScript-first DX is now available in Preview. To learn more, please visit AWS Amplify (Gen 2). > > To open a new issue related to Amplify's new backend building experience, please visit AWS Amplify Backend.

AWS Amplify CLI

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

Requires Node.js® version 18 or later

Install and configure the Amplify CLI as follows:

$ npm install -g @aws-amplify/cli
$ 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 ``	Adds cloud features to your app.
amplify update ``	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 [ ``...]	Displays the state of local resources that haven't been pushed to the cloud (Create/Update/Delete).
amplify status -v [ ``...]	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 `` 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:

cd 
amplify-dev init
amplify-dev

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.

@aws-amplify/amplify-category-custom dependencies

@aws-amplify/amplify-cli-core @aws-amplify/amplify-prompts aws-cdk-lib execa fs-extra glob ora uuid

@aws-amplify/amplify-category-custom development dependencies

@types/lodash jest rimraf

FAQs

What is @aws-amplify/amplify-category-custom?

amplify-cli custom resources plugin. Visit Snyk Advisor to see a full health score report for @aws-amplify/amplify-category-custom, including popularity, security, maintenance & community analysis.

Is @aws-amplify/amplify-category-custom popular?

The npm package @aws-amplify/amplify-category-custom receives a total of 67,135 weekly downloads. As such, @aws-amplify/amplify-category-custom popularity was classified as a popular. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @aws-amplify/amplify-category-custom well maintained?

We found that @aws-amplify/amplify-category-custom demonstrated a healthy version release cadence and project activity. It has a community of 270 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is @aws-amplify/amplify-category-custom safe to use?

While scanning the latest version of @aws-amplify/amplify-category-custom, we found that a security review is needed. A total of 0 vulnerabilities or license issues were detected. See the full security scan results.

Last updated on 18 April-2024, at 07:29 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP