Is extract-npm-package-config safe to use?

extract-npm-package-config has no known vulnerabilities on the latest version (0.1.2). DepScope rates its health at 39/100 (critical risk).

What is the latest version of extract-npm-package-config?

The latest version of extract-npm-package-config is 0.1.2, released 2017-12-06.

Does extract-npm-package-config have known vulnerabilities?

No known vulnerabilities on the latest version of extract-npm-package-config.

Is extract-npm-package-config deprecated?

No, extract-npm-package-config is actively maintained. Latest release: 0.1.2 (2017-12-06).

What are alternatives to extract-npm-package-config?

Popular alternatives to extract-npm-package-config in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does extract-npm-package-config use?

extract-npm-package-config is licensed under MIT.

extract-npm-package-config

npmv0.1.2

Extract npm package config variables from process.env for in-app usage

License MITpermissive2 versions1 maintainers1 deps3 weekly dl

lutangar/extract-npm-package-config

/ 100

Health

use with caution

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

Moderate health score (39/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

lodash.isnumber

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/extract-npm-package-config