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

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

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

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

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

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

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

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

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

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

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

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

@acoustic-content-sdk/component-edit

npmv9.0.10076

Framework independent collection of utilities to implement inline edit.

License MITpermissive19 versions5 maintainers3 deps79 weekly dl

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/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 (3)

@acoustic-content-sdk/api @acoustic-content-sdk/edit-api @acoustic-content-sdk/utils

API access

Get this data programmatically — free, no authentication.

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