Is @neo-one/node-neo-settings safe to use?

@neo-one/node-neo-settings has no known vulnerabilities on the latest version (2.7.4). DepScope rates its health at 43/100 (high risk).

What is the latest version of @neo-one/node-neo-settings?

The latest version of @neo-one/node-neo-settings is 2.7.4, released 2021-09-14.

Does @neo-one/node-neo-settings have known vulnerabilities?

No known vulnerabilities on the latest version of @neo-one/node-neo-settings.

Is @neo-one/node-neo-settings deprecated?

No, @neo-one/node-neo-settings is actively maintained. Latest release: 2.7.4 (2021-09-14).

What are alternatives to @neo-one/node-neo-settings?

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

What license does @neo-one/node-neo-settings use?

License information for @neo-one/node-neo-settings is not declared in the registry metadata.

@neo-one/node-neo-settings

npmv2.7.4

NEO•ONE standard MainNet and TestNet blockchain settings.

145 versions2 maintainers8 deps43 weekly dl

/ 100

Health

use with caution

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

Moderate health score (43/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

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

@neo-one/client-common @neo-one/node-core @neo-one/utils @types/bn.js @types/lodash bn.js lodash tslib

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@neo-one/node-neo-settings