Is @neo-one/client-full-common safe to use?

@neo-one/client-full-common has no known vulnerabilities on the latest version (2.7.3). DepScope rates its health at 49/100 (high risk).

What is the latest version of @neo-one/client-full-common?

The latest version of @neo-one/client-full-common is 2.7.3, released 2021-06-15.

Does @neo-one/client-full-common have known vulnerabilities?

No known vulnerabilities on the latest version of @neo-one/client-full-common.

Is @neo-one/client-full-common deprecated?

No, @neo-one/client-full-common is actively maintained. Latest release: 2.7.3 (2021-06-15).

What are alternatives to @neo-one/client-full-common?

Popular alternatives to @neo-one/client-full-common in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @neo-one/client-full-common use?

License information for @neo-one/client-full-common is not declared in the registry metadata.

@neo-one/client-full-common

npmv2.7.3

NEO•ONE full client common code.

63 versions2 maintainers3 deps1,288 weekly dl

/ 100

Health

use with caution

@neo-one/[email protected] low health (49/100) — consider alternatives

Moderate health score (49/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

15/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (3)

@neo-one/client-common @neo-one/utils tslib

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@neo-one/client-full-common