Is executing-npm-path safe to use?

executing-npm-path has no known vulnerabilities on the latest version (1.0.0). DepScope rates its health at 42/100 (high risk).

What is the latest version of executing-npm-path?

The latest version of executing-npm-path is 1.0.0, released 2018-06-18.

Does executing-npm-path have known vulnerabilities?

No known vulnerabilities on the latest version of executing-npm-path.

Is executing-npm-path deprecated?

No, executing-npm-path is actively maintained. Latest release: 1.0.0 (2018-06-18).

What are alternatives to executing-npm-path?

Popular alternatives to executing-npm-path in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does executing-npm-path use?

executing-npm-path is licensed under ISC.

executing-npm-path

npmv1.0.0

A path of the currently executed npm CLI

License ISCpermissive3 versions1 maintainers0 deps923 weekly dl

shinnn/executing-npm-path

/ 100

Health

use with caution

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

Moderate health score (42/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

0.3 KBminified

0.2 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/executing-npm-path