Is merge-source-map safe to use?

merge-source-map has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 59/100 (high risk).

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

The latest version of merge-source-map is 1.1.0, released 2017-12-25.

Does merge-source-map have known vulnerabilities?

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

Is merge-source-map deprecated?

No, merge-source-map is actively maintained. Latest release: 1.1.0 (2017-12-25).

What are alternatives to merge-source-map?

Popular alternatives to merge-source-map in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does merge-source-map use?

merge-source-map is licensed under MIT.

merge-source-map

npmv1.1.0

Merge old source map and new source map in multi-transform flow

License MITpermissive6 versions1 maintainers1 deps3,265,787 weekly dl

keik/merge-source-map

/ 100

Health

use with caution

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

Moderate health score (59/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

15/15

maturity

2/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

26.6 KBminified

7.8 KB gzipped

1 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Quality signals

OSS Criticality

0.68high

Health History

Dependency Tree

License Audit

Dependencies (1)

source-map

API access

Get this data programmatically — free, no authentication.

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