Is @nwaltham/nconf safe to use?

@nwaltham/nconf has no known vulnerabilities on the latest version (0.8.6). DepScope rates its health at 39/100 (critical risk).

What is the latest version of @nwaltham/nconf?

The latest version of @nwaltham/nconf is 0.8.6, released 2016-10-08.

Does @nwaltham/nconf have known vulnerabilities?

No known vulnerabilities on the latest version of @nwaltham/nconf.

Is @nwaltham/nconf deprecated?

No, @nwaltham/nconf is actively maintained. Latest release: 0.8.6 (2016-10-08).

What are alternatives to @nwaltham/nconf?

Popular alternatives to @nwaltham/nconf in npm include: minimatch, chalk, commander, picomatch, eslint-visitor-keys.

What license does @nwaltham/nconf use?

@nwaltham/nconf is licensed under MIT.

@nwaltham/nconf

npmv0.8.6

Hierarchical node.js configuration with files, environment variables, command-line arguments, and atomic object merging.

License MITpermissive3 versions1 maintainers4 deps

ssh://[email protected]/nwaltham/nconf

/ 100

Health

use with caution

@nwaltham/[email protected] low health (39/100) — consider alternatives

Low health score (39/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

64.3 KBminified

21.2 KB gzipped

4 direct dependencies

side effectsscoped

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (4)

async ini secure-keys yargs

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@nwaltham/nconf