merge-stream

v2.0.0

Create a stream that emits events from multiple other streams For more information about how to use this package see README

Latest version published 4 years ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

71 / 100

Security

No known security issues
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
2.0.0 | 05/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.1 | 11/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.8 | 06/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.1 | 05/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Influential project

Weekly Downloads (19,990,163)

Download trend
Dependents
3.09K
GitHub Stars
210
Forks
16
Contributors
10

Direct Usage Popularity

TOP 5%

The npm package merge-stream receives a total of 19,990,163 downloads a week. As such, we scored merge-stream popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package merge-stream, we found that it has been starred 210 times, and that 3,092 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
10
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like merge-stream is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 71/100 package health 71/100

Maintenance

Sustainable

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
0
Last Release
4 years ago
Last Commit
3 years ago

Further analysis of the maintenance status of merge-stream based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

An important project maintenance signal to consider for merge-stream is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
not defined

Age
9 years
Dependencies
0 Direct
Versions
15
Install Size
4.31 kB
Dist-tags
1
# of Files
4
Maintainers
3
TS Typings
Yes

merge-stream has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.