Is @adobe/aem-spa-component-mapping safe to use?

@adobe/aem-spa-component-mapping has no known vulnerabilities on the latest version (1.1.1). DepScope rates its health at 52/100 (high risk).

What is the latest version of @adobe/aem-spa-component-mapping?

The latest version of @adobe/aem-spa-component-mapping is 1.1.1, released 2021-04-15.

Does @adobe/aem-spa-component-mapping have known vulnerabilities?

No known vulnerabilities on the latest version of @adobe/aem-spa-component-mapping.

Is @adobe/aem-spa-component-mapping deprecated?

No, @adobe/aem-spa-component-mapping is actively maintained. Latest release: 1.1.1 (2021-04-15).

What are alternatives to @adobe/aem-spa-component-mapping?

Popular alternatives to @adobe/aem-spa-component-mapping in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @adobe/aem-spa-component-mapping use?

@adobe/aem-spa-component-mapping is licensed under Apache-2.0.

@adobe/aem-spa-component-mapping

npmv1.1.1

Provides a mapping of SPA front-end components to AEM resource types.

License Apache-2.0permissive11 versions31 maintainers0 deps18,925 weekly dl

adobe/aem-spa-component-mapping

/ 100

Health

use with caution

@adobe/[email protected] low health (52/100) — consider alternatives

Moderate health score (52/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

12/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@adobe/aem-spa-component-mapping