Is to-regex-range safe to use?

to-regex-range has no known vulnerabilities on the latest version (5.0.1). DepScope rates its health at 43/100 (high risk).

What is the latest version of to-regex-range?

The latest version of to-regex-range is 5.0.1, released 2019-04-07.

Does to-regex-range have known vulnerabilities?

No known vulnerabilities on the latest version of to-regex-range.

Is to-regex-range deprecated?

No, to-regex-range is actively maintained. Latest release: 5.0.1 (2019-04-07).

What are alternatives to to-regex-range?

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

What license does to-regex-range use?

to-regex-range is licensed under MIT.

to-regex-range

npmv5.0.1

Pass two numbers, get a regex-compatible source string for matching ranges. Validated against more than 2.78 million test assertions.

License MITpermissive18 versions2 maintainers1 deps

micromatch/to-regex-range

/ 100

Health

safe to use

[email protected] is safe to use (health: 43/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

2.9 KBminified

1.4 KB gzipped

1 direct dependencies

side effects

🌟

TypeScript

7/10typed

Types from @types/to-regex-range (DefinitelyTyped)

OSS Scorecard

OpenSSF security posture score

3.0/10

weak

Maintainer trust

Active maintainers (3m)

1

Contributors (12m)

0

Primary author dominance

0%

GitHub stars

172

single active maintainer 3m

Quality signals

OSS Criticality

0.80critical

Download trend

stable(+3.5%)

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (1)

is-number

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/to-regex-range