Is source-map-resolve safe to use?

source-map-resolve has no known vulnerabilities on the latest version (0.6.0). DepScope rates its health at 12/100 (critical risk).

What is the latest version of source-map-resolve?

The latest version of source-map-resolve is 0.6.0, released 2020-03-21.

Does source-map-resolve have known vulnerabilities?

No known vulnerabilities on the latest version of source-map-resolve.

Is source-map-resolve deprecated?

Yes, source-map-resolve is deprecated: See https://github.com/lydell/source-map-resolve#deprecated Consider using debug instead.

What are alternatives to source-map-resolve?

Popular alternatives to source-map-resolve in npm include: debug, lru-cache, string-width, commander, picomatch.

What license does source-map-resolve use?

source-map-resolve is licensed under MIT.

source-map-resolve

npmv0.6.0deprecated

Resolve the source map and/or sources for a generated file.

License MITpermissive14 versions1 maintainers2 deps

lydell/source-map-resolve

/ 100

Health

find alternative

source-map-resolve is deprecated — find an alternative

Low health score (12/100)
Package is deprecated

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

Quality signals

Download trend

stable(0%)

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (2)

atob decode-uri-component

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/source-map-resolve