Is current-module-paths safe to use?

current-module-paths has no known vulnerabilities on the latest version (1.1.3). DepScope rates its health at 63/100 (moderate risk).

What is the latest version of current-module-paths?

The latest version of current-module-paths is 1.1.3, released 2025-11-09.

Does current-module-paths have known vulnerabilities?

No known vulnerabilities on the latest version of current-module-paths.

Is current-module-paths deprecated?

No, current-module-paths is actively maintained. Latest release: 1.1.3 (2025-11-09).

What are alternatives to current-module-paths?

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

What license does current-module-paths use?

current-module-paths is licensed under MIT.

current-module-paths

npmv1.1.3

Access to __filename and __dirname within ECMAScript modules

License MITpermissive6 versions1 maintainers0 deps208,786 weekly dl

75lb/current-module-paths

/ 100

Health

use with caution

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

Moderate health score (63/100) — verify manually

Health breakdown0 – 100

10/25

maintenance

14/20

popularity

25/25

security

12/15

maturity

2/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

0.4 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/current-module-paths