end-of-stream

v1.4.4

Call a callback when a readable/writable/duplex stream has completed or failed.

MIT
Latest version published 3 years ago
    npm install end-of-stream
  

Package Health Score

67 / 100

Security

No known security issues
Powered by Snyk
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
1.4.4 | 09/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.0 | 03/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.5 | 06/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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test end-of-stream
Get started free

Popularity

Influential project

Weekly Downloads (27,566,824)

Download trend
Dependents
769
GitHub Stars
142
Forks
25
Contributors
8

Direct Usage Popularity

TOP 5%

The npm package end-of-stream receives a total of 27,566,824 downloads a week. As such, we scored end-of-stream popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package end-of-stream, we found that it has been starred 142 times, and that 769 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
8
Funding
Yes

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 67/100 package health 67/100

Maintenance

Inactive

Commit Frequency

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

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

An important project maintenance signal to consider for end-of-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
1 Direct
Versions
16
Install Size
6.23 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
Yes

end-of-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.