Is @sindresorhus/merge-streams safe to use?

@sindresorhus/merge-streams has no known vulnerabilities on the latest version (4.0.0). DepScope rates its health at 56/100 (high risk).

What is the latest version of @sindresorhus/merge-streams?

The latest version of @sindresorhus/merge-streams is 4.0.0, released 2024-05-04.

Does @sindresorhus/merge-streams have known vulnerabilities?

No known vulnerabilities on the latest version of @sindresorhus/merge-streams.

Is @sindresorhus/merge-streams deprecated?

No, @sindresorhus/merge-streams is actively maintained. Latest release: 4.0.0 (2024-05-04).

What are alternatives to @sindresorhus/merge-streams?

Popular alternatives to @sindresorhus/merge-streams in npm include: semver, ansi-styles, debug, minimatch, brace-expansion.

What license does @sindresorhus/merge-streams use?

@sindresorhus/merge-streams is licensed under MIT.

@sindresorhus/merge-streams

npmv4.0.0

Merge multiple streams into a unified stream

License MITpermissive11 versions1 maintainers0 deps23,900,221 weekly dl

sindresorhus/merge-streams

/ 100

Health

use with caution

@sindresorhus/[email protected] low health (56/100) — consider alternatives

Moderate health score (56/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

20/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Quality signals

OSS Criticality

0.61high

Download trend

stable(0%)

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@sindresorhus/merge-streams