npmpackage.info

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

@aws-amplify/core

A declarative JavaScript library for application development using cloud services.

6.7.0

9,438

Apache-2.0

TypeScript

144,296,098 7.2

Installations

npm install @aws-amplify/core

Pull Requests

Open

56

Total

5,179

Closed

995

Merged

4,128

Issues

Open

541

Total

6,620

Closed

6,079

Releases

166

2024-11-25 Amplify JS release - aws-amplify@6.10.0

aws-amplify@6.10.0

Published on 25 Nov 2024

2024-11-20 Amplify JS release - aws-amplify@6.9.0

aws-amplify@6.9.0

Published on 20 Nov 2024

aws-amplify@6.8.2

Published on 13 Nov 2024

aws-amplify@6.8.1

Published on 13 Nov 2024

2024-10-31 Amplify JS release - aws-amplify@6.8.0

aws-amplify@6.8.0

Published on 01 Nov 2024

2024-10-30 Amplify JS release - aws-amplify@6.7.0

aws-amplify@6.7.0

Published on 30 Oct 2024

View all 166 releases

Developer

aws-amplify

Developer Guide

BETA

Module System

CommonJS, ESM

Min. Node Version

Typescript Support

No

Node Version

18.20.2

NPM Version

lerna/7.4.2/node@v18.20.2+x64 (linux)

Statistics

9,438 Stars

9,756 Commits

2,133 Forks

213 Watching

92 Branches

480 Contributors

Updated on 26 Nov 2024

Languages

TypeScript (92.68%)

C (3.67%)

JavaScript (1.25%)

Kotlin (1.12%)

Swift (0.48%)

Objective-C (0.47%)

Java (0.12%)

Ruby (0.1%)

Shell (0.09%)

Objective-C++ (0.03%)

Total Downloads

Cumulative downloads

Total Downloads

144,296,098

Last day

-8.1%

171,460

Compared to previous day

Last week

-0.5%

952,523

Compared to previous week

Last month

4,135,048

Compared to previous month

Last year

16%

44,845,445

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

rxjs uuid tslib js-cookie @types/uuid @aws-sdk/types @aws-crypto/sha256-js @smithy/util-hex-encoding

Dev Dependencies

genversion typescript @types/js-cookie @aws-amplify/react-native

Versions

Reporting Bugs / Feature Requests

Note aws-amplify 6 has been released. If you are looking for upgrade guidance click here

AWS Amplify is a JavaScript library for frontend and mobile developers building cloud-enabled applications

AWS Amplify provides a declarative and easy-to-use interface across different categories of cloud operations. AWS Amplify goes well with any JavaScript based frontend workflow and React Native for mobile developers.

Our default implementation works with Amazon Web Services (AWS), but AWS Amplify is designed to be open and pluggable for any custom backend or service.

Visit our documentation site to learn more about AWS Amplify. Please see the Amplify JavaScript page for information around the full list of features we support.

Contributing

Features

Category	AWS Provider	Description
Authentication	Amazon Cognito	APIs and Building blocks to create Authentication experiences.
Analytics	Amazon Pinpoint	Collect Analytics data for your application including tracking user sessions.
REST API	Amazon API Gateway	Sigv4 signing and AWS auth for API Gateway and other REST endpoints.
GraphQL API	AWS AppSync	Interact with your GraphQL or AWS AppSync endpoint(s).
DataStore	AWS AppSync	Programming model for shared and distributed data, with simple online/offline synchronization.
Storage	Amazon S3	Manages content in public, protected, private storage buckets.
Geo (Developer preview)	Amazon Location Service	Provides APIs and UI components for maps and location search for JavaScript-based web apps.
Push Notifications	Amazon Pinpoint	Allows you to integrate push notifications in your app with Amazon Pinpoint targeting and campaign management support.
Interactions	Amazon Lex	Create conversational bots powered by deep learning technologies.
PubSub	AWS IoT	Provides connectivity with cloud-based message-oriented middleware.
Internationalization	---	A lightweight internationalization solution.
Cache	---	Provides a generic LRU cache for JavaScript developers to store data with priority and expiration settings.
Predictions	Various*	Connect your app with machine learning services like NLP, computer vision, TTS, and more.

Predictions utilizes a range of Amazon's Machine Learning services, including: Amazon Comprehend, Amazon Polly, Amazon Rekognition, Amazon Textract, and Amazon Translate.

Getting Started

AWS Amplify is available as aws-amplify on npm.

To get started pick your platform from our Getting Started home page

Notice:

Amplify 6.x.x has breaking changes. Please see the breaking changes on our migration guide

Amplify 5.x.x has breaking changes. Please see the breaking changes below:

If you are using default exports from any Amplify package, then you will need to migrate to using named exports. For example:

1- import Amplify from 'aws-amplify';
2+ import { Amplify } from 'aws-amplify'
3
4- import Analytics from '@aws-amplify/analytics';
5+ import { Analytics } from '@aws-amplify/analytics';
6// or better
7+ import { Analytics } from 'aws-amplify';
8
9- import Storage from '@aws-amplify/storage';
10+ import { Storage } from '@aws-amplify/storage';
11// or better
12+ import { Storage } from 'aws-amplify';

Datastore predicate syntax has changed, impacting the DataStore.query, DataStore.save, DataStore.delete, and DataStore.observe interfaces. For example:
```
1- await DataStore.delete(Post, (post) => post.status('eq', PostStatus.INACTIVE));
2+ await DataStore.delete(Post, (post) => post.status.eq(PostStatus.INACTIVE));
3
4- await DataStore.query(Post, p => p.and( p => [p.title('eq', 'Amplify Getting Started Guide'), p.score('gt', 8)]));
5+ await DataStore.query(Post, p => p.and( p => [p.title.eq('Amplify Getting Started Guide'), p.score.gt(8)]));
```
- To use the new syntax with 5.x.x you may need to rebuild your Datastore models with the latest version of Amplify codegen. To do this:
  - Upgrade the Amplify CLI
    - npm install -g @aws-amplify/cli
  - Re-generate your models with Amplify codegen
    - amplify codegen models

Storage.list has changed the name of the maxKeys parameter to pageSize and has a new return type that contains the results list. For example:

1- const photos = await Storage.list('photos/', { maxKeys: 100 });
2- const { key } = photos[0];
3
4+ const photos = await Storage.list('photos/', { pageSize: 100 });
5+ const { key } = photos.results[0];

Storage.put with resumable turned on has changed the key to no longer include the bucket name. For example:

1- let uploadedObjectKey;
2- Storage.put(file.name, file, {
3-   resumable: true,
4-   // Necessary to parse the bucket name out to work with the key
5-   completeCallback: (obj) => uploadedObjectKey = obj.key.substring( obj.key.indexOf("/") + 1 )
6- }
7
8+ let uploadedObjectKey;
9+ Storage.put(file.name, file, {
10+   resumable: true,
11+   completeCallback: (obj) => uploadedObjectKey = obj.key
12+ }

Analytics.record no longer accepts string as input. For example:

1- Analytics.record('my example event');
2+ Analytics.record({ name: 'my example event' });

The JS export has been removed from @aws-amplify/core in favor of exporting the functions it contained.

Any calls to Amplify.Auth, Amplify.Cache, and Amplify.ServiceWorker are no longer supported. Instead, your code should use the named exports. For example:

1- import { Amplify } from 'aws-amplify';
2- Amplify.configure(...);
3- // ...
4- Amplify.Auth.signIn(...);
5
6+ import { Amplify, Auth } from 'aws-amplify';
7+ Amplify.configure(...);
8+ // ...
9+ Auth.signIn(...);

Amplify 4.x.x has breaking changes for React Native. Please see the breaking changes below:

If you are using React Native (vanilla or Expo), you will need to add the following React Native community dependencies:
- @react-native-community/netinfo
- @react-native-async-storage/async-storage

// React Native
yarn add aws-amplify amazon-cognito-identity-js @react-native-community/netinfo @react-native-async-storage/async-storage
npx pod-install

// Expo
yarn add aws-amplify @react-native-community/netinfo @react-native-async-storage/async-storage

Amplify 3.x.x has breaking changes. Please see the breaking changes below:

AWS.credentials and AWS.config don’t exist anymore in Amplify JavaScript.
- Both options will not be available to use in version 3. You will not be able to use and set your own credentials.
- For more information on this change, please see the AWS SDK for JavaScript v3
aws-sdk@2.x has been removed from Amplify@3.x.x in favor of version 3 of aws-sdk-js. We recommend to migrate to aws-sdk-js-v3 if you rely on AWS services that are not supported by Amplify, since aws-sdk-js-v3 is imported modularly.

If you can't migrate to aws-sdk-js-v3 or rely on aws-sdk@2.x, you will need to import it separately.

If you are using exported paths within your Amplify JS application, (e.g. import from "@aws-amplify/analytics/lib/Analytics") this will now break and no longer will be supported. You will need to change to named imports:
```
1import { Analytics } from 'aws-amplify';
```
If you are using categories as Amplify.<Category>, this will no longer work and we recommend to import the category you are needing to use:
```
1import { Auth } from 'aws-amplify';
```

DataStore Docs

For more information on contributing to DataStore / how DataStore works, see the DataStore Docs

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.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

6

Binary-Artifacts

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

5

Pinned-Dependencies

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

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.

Reason

detected GitHub workflow tokens with excessive permissions

Details

Info: jobLevel 'actions' permission set to 'read': .github/workflows/codeql.yml:18
Info: jobLevel 'contents' permission set to 'read': .github/workflows/codeql.yml:19
Warn: jobLevel 'contents' permission set to 'write': .github/workflows/push-latest-release.yml:18
Warn: jobLevel 'contents' permission set to 'write': .github/workflows/push-lts-release.yml:21
Info: jobLevel 'actions' permission set to 'read': .github/workflows/snyk-security.yml:18
Info: jobLevel 'contents' permission set to 'read': .github/workflows/snyk-security.yml:16
Warn: no topLevel permission defined: .github/workflows/aws-amplify-dependency-check.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-bundle-size-tests.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-canary-e2e-runner.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-canary-e2e-tests.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-canary-e2e.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-canary-sampleapp-tests.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-dependency-review.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-e2e-test-detox.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-e2e-test-headless.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-e2e-test.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-e2e-tests.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-get-package-list.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-npm-publish-lts-release.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-npm-publish-preid.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-npm-publish-release.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-prebuild-amplify-js.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-prebuild-samples-staging.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-release-verification.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-test-github-actions.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-test-license.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-test-tsc-compliance.yml:1
Warn: no topLevel permission defined: .github/workflows/callable-unit-tests.yml:1
Warn: no topLevel permission defined: .github/workflows/codeql.yml:1
Warn: no topLevel permission defined: .github/workflows/issue-comment.yml:1
Warn: no topLevel permission defined: .github/workflows/issue-labeled.yml:1
Warn: no topLevel permission defined: .github/workflows/issue-opened.yml:1
Warn: no topLevel permission defined: .github/workflows/lock.yaml:1
Warn: no topLevel permission defined: .github/workflows/on-schedule-canary-test.yml:1
Info: topLevel permissions set to 'read-all': .github/workflows/pr.yml:9
Warn: no topLevel permission defined: .github/workflows/push-integ-test.yml:1
Warn: no topLevel permission defined: .github/workflows/push-latest-release.yml:1
Warn: no topLevel permission defined: .github/workflows/push-lts-release.yml:1
Warn: no topLevel permission defined: .github/workflows/push-main-release.yml:1
Warn: no topLevel permission defined: .github/workflows/push-next-release.yml:1
Warn: no topLevel permission defined: .github/workflows/push-preid-release.yml:1
Info: topLevel 'contents' permission set to 'read': .github/workflows/snyk-security.yml:10

0

Fuzzing

Determines if the project uses fuzzing.

Score

7.2

/10

Last Scanned on 2024-11-25

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