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

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

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

The latest version of @neo-one/client-full-common-browserify is 2.3.0, released 2019-10-23.

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

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

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

No, @neo-one/client-full-common-browserify is actively maintained. Latest release: 2.3.0 (2019-10-23).

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

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

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

@neo-one/client-full-common-browserify is licensed under MIT.

@neo-one/client-full-common-browserify

npmv2.3.0

NEO•ONE full client common code.

License MITpermissive12 versions2 maintainers3 deps14 weekly dl

neo-one-suite/neo-one

40

/ 100

Health

use with caution

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

Moderate health score (40/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

0

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

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

API access

Get this data programmatically — free, no authentication.

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