Is @aws-amplify/client-config safe to use?

@aws-amplify/client-config has no known vulnerabilities on the latest version (1.10.1). DepScope rates its health at 68/100 (moderate risk).

What is the latest version of @aws-amplify/client-config?

The latest version of @aws-amplify/client-config is 1.10.1, released 2026-03-11.

Does @aws-amplify/client-config have known vulnerabilities?

No known vulnerabilities on the latest version of @aws-amplify/client-config.

Is @aws-amplify/client-config deprecated?

No, @aws-amplify/client-config is actively maintained. Latest release: 1.10.1 (2026-03-11).

What are alternatives to @aws-amplify/client-config?

Popular alternatives to @aws-amplify/client-config in npm include: debug, chalk, picomatch, source-map, has-flag.

What license does @aws-amplify/client-config use?

@aws-amplify/client-config is licensed under Apache-2.0.

@aws-amplify/client-config

npmv1.10.1

Responsible for translating stack outputs and metadata (read via the [deployed-backend-client](../deployed-backend-client/README.md)) into client config that can be consumed by the Amplify frontend libraries.

License Apache-2.0permissive142 versions6 maintainers6 deps

aws-amplify/amplify-backend

/ 100

Health

safe to use

@aws-amplify/[email protected] is safe to use (health: 68/100)

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

8/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (6)

@aws-amplify/backend-output-schemas @aws-amplify/deployed-backend-client @aws-amplify/model-generator @aws-amplify/platform-core @aws-amplify/plugin-types zod

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@aws-amplify/client-config