Is @acoustic-content-sdk/component-api safe to use?

@acoustic-content-sdk/component-api has no known vulnerabilities on the latest version (9.0.10076). DepScope rates its health at 45/100 (high risk).

What is the latest version of @acoustic-content-sdk/component-api?

The latest version of @acoustic-content-sdk/component-api is 9.0.10076, released 2020-03-26.

Does @acoustic-content-sdk/component-api have known vulnerabilities?

No known vulnerabilities on the latest version of @acoustic-content-sdk/component-api.

Is @acoustic-content-sdk/component-api deprecated?

No, @acoustic-content-sdk/component-api is actively maintained. Latest release: 9.0.10076 (2020-03-26).

What are alternatives to @acoustic-content-sdk/component-api?

Popular alternatives to @acoustic-content-sdk/component-api in npm include: semver, ansi-styles, debug, minimatch, brace-expansion.

What license does @acoustic-content-sdk/component-api use?

@acoustic-content-sdk/component-api is licensed under MIT.

@acoustic-content-sdk/component-api

npmv9.0.10076

Module to attach inline-edit functionality to an WCH based Angular application.

License MITpermissive19 versions5 maintainers1 deps144 weekly dl

/ 100

Health

safe to use

@acoustic-content-sdk/[email protected] is safe to use (health: 45/100)

Health breakdown0 – 100

0/25

maintenance

3/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

Dependencies (1)

@acoustic-content-sdk/api

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@acoustic-content-sdk/component-api