Is common-path-prefix safe to use?

common-path-prefix has no known vulnerabilities on the latest version (3.0.0). DepScope rates its health at 62/100 (moderate risk).

What is the latest version of common-path-prefix?

The latest version of common-path-prefix is 3.0.0, released 2019-11-03.

Does common-path-prefix have known vulnerabilities?

No known vulnerabilities on the latest version of common-path-prefix.

Is common-path-prefix deprecated?

No, common-path-prefix is actively maintained. Latest release: 3.0.0 (2019-11-03).

What are alternatives to common-path-prefix?

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

What license does common-path-prefix use?

common-path-prefix is licensed under ISC.

common-path-prefix

npmv3.0.0

Computes the longest prefix string that is common to each path, excluding the base component

License ISCpermissive3 versions1 maintainers0 deps11,191,620 weekly dl

novemberborn/common-path-prefix

/ 100

Health

use with caution

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

Moderate health score (62/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

20/20

popularity

25/25

security

15/15

maturity

2/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

0.5 KBminified

0.3 KB gzipped

0 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Quality signals

Download trend

stable(0%)

Publish security

npm signed

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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