Is http-range-parse safe to use?

http-range-parse 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 http-range-parse?

The latest version of http-range-parse is 1.0.0, released 2014-07-21.

Does http-range-parse have known vulnerabilities?

No known vulnerabilities on the latest version of http-range-parse.

Is http-range-parse deprecated?

No, http-range-parse is actively maintained. Latest release: 1.0.0 (2014-07-21).

What are alternatives to http-range-parse?

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

What license does http-range-parse use?

http-range-parse is licensed under MIT.

http-range-parse

npmv1.0.0

Parse HTTP Range header, based on RFC7233

License MITpermissive2 versions1 maintainers0 deps

git://github.com/purposeindustries/node-http-range-parse

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

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/http-range-parse