Make sure the open source you're using is safe to use
pump
v3.0.0pipe streams together and close all of them if one of them closes
npm install pump
Explore Similar Packages
Package Health Score
55 / 100
- Popularity Influential project
- Maintenance Inactive
- Security No known security issues
- Community Limited
Make sure the open source you're using is safe to usePopularity
Influential project
Weekly Downloads (33,028,562)- Dependents
- 2.65K
- GitHub Stars
- 810
- Forks
- 52
- Contributors
- 6
The npm package pump receives a total of 33,028,562 downloads a week. As such, we scored pump popularity level to be Influential project.
Based on project statistics from the GitHub repository for the npm package pump, we found that it has been starred 810 times, and that 2,645 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.
Security
No known security issues
Security and license risk for significant versions
All VersionsDirect Vulnerabilities
0.2.3
0.3.5
1.0.3
2.0.1
3.0.0
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
Indirect Vulnerabilities
0.2.3
0.3.5
1.0.3
2.0.1
3.0.0
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
License Risks
0.2.3
0.3.5
1.0.3
2.0.1
3.0.0
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
All security vulnerabilities belong to
production dependencies of direct and indirect
packages.
We found a way for you to contribute to the project! Looks like pump is missing a security policy.
You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.
We found a way for you to contribute to the project! Looks like pump is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test pump
Maintenance
Inactive
Commit Frequency- Open Issues
- 12
- Merged PR
- 4
- Open PR
- 5
- Last Commit
- 7 months ago
Further analysis of the maintenance status of pump 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 pump 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.
Community
Limited
- Readme.md
- Yes
- Contributing.md
- No
- Code of Conduct
- No
- Contributors
- 6
- Funding
- Yes
This project has seen only 10 or less contributors.
We found a way for you to contribute to the project! Looks like pump is missing a Code of Conduct.
Embed Package Health Score Badge
Package
- Node.js Compatibility
- not defined
- Age
- 7 years
- Dependencies
- 2 Direct
- Versions
- 26
- Install Size
- 0 B
- Dist-tags
- 1
- # of Files
- 0
- Maintainers
- 1
- TS Typings
- Yes
pump 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.
pump
pump is a small node module that pipes streams together and destroys all of them if one of them closes.
npm install pump
What problem does it solve?
When using standard source.pipe(dest) source will not be destroyed if dest emits close or an error.
You are also not able to provide a callback to tell when then pipe has finished.
pump does these two things for you
Usage
Simply pass the streams you want to pipe together to pump and add an optional callback
var pump = require('pump')
var fs = require('fs')
var source = fs.createReadStream('/dev/random')
var dest = fs.createWriteStream('/dev/null')
pump(source, dest, function(err) {
console.log('pipe finished', err)
})
setTimeout(function() {
dest.destroy() // when dest is closed pump will destroy source
}, 1000)
You can use pump to pipe more than two streams together as well
var transform = someTransformStream()
pump(source, transform, anotherTransform, dest, function(err) {
console.log('pipe finished', err)
})
If source, transform, anotherTransform or dest closes all of them will be destroyed.
Similarly to stream.pipe(), pump() returns the last stream passed in, so you can do:
return pump(s1, s2) // returns s2
If you want to return a stream that combines both s1 and s2 to a single stream use pumpify instead.
License
MIT
Related
pump is part of the mississippi stream utility collection which includes more useful stream modules similar to this one.
pump versions
| Version | Published | Tag | Node.js Compatability | Licenses | Dependencies | Direct Vulnerabilities | Publisher |
|---|---|---|---|---|---|---|---|
| 3.0.0 | 31 January 2018 | latest | * | MIT | 2 |
| mafintosh |
| 2.0.1 | 22 January 2018 | * | MIT | 2 |
| mafintosh | |
| 1.0.3 | 16 November 2017 | * | MIT | 2 |
| mafintosh | |
| All Versions | |||||||
pump dependencies
Last updated on
22 January-2021, at 22:01 (UTC).