Is current-path-require safe to use?

current-path-require 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 current-path-require?

The latest version of current-path-require is 0.1.2, released 2016-07-26.

Does current-path-require have known vulnerabilities?

No known vulnerabilities on the latest version of current-path-require.

Is current-path-require deprecated?

No, current-path-require is actively maintained. Latest release: 0.1.2 (2016-07-26).

What are alternatives to current-path-require?

Popular alternatives to current-path-require in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does current-path-require use?

current-path-require is licensed under ISC.

current-path-require

npmv0.1.2

require modules from current path

License ISCpermissive3 versions1 maintainers1 deps13 weekly dl

dzy321/current-path-require

/ 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)

require-relative

API access

Get this data programmatically — free, no authentication.

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