Make sure the open source you're using is safe to use
destroy
v1.0.4destroy a stream if possible
npm install destroy
Explore Similar Packages
Package Health Score
53 / 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 (15,009,774)- Dependents
- 374
- GitHub Stars
- 47
- Forks
- 5
- Contributors
- 3
The npm package destroy receives a total of 15,009,774 downloads a week. As such, we scored destroy popularity level to be Influential project.
Based on project statistics from the GitHub repository for the npm package destroy, we found that it has been starred 47 times, and that 374 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
1.0.4
- 0H
- 0M
- 0L
Indirect Vulnerabilities
1.0.4
- 0H
- 0M
- 0L
License Risks
1.0.4
- 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 destroy 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 destroy is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test destroy
Maintenance
Inactive
Commit Frequency- Open Issues
- 0
- Merged PR
- 1
- Open PR
- 2
- Last Commit
- 2 years ago
Further analysis of the maintenance status of destroy 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 destroy 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
- No
- Contributing.md
- No
- Code of Conduct
- No
- Contributors
- 3
- Funding
- No
This project has seen only 10 or less contributors.
We found a way for you to contribute to the project! Looks like destroy is missing a Code of Conduct.
How about a good first contribution to this project? It seems that destroy is missing a README file.
Embed Package Health Score Badge
Package
- Node.js Compatibility
- not defined
- Age
- 7 years
- Dependencies
- 0 Direct / 0 Total
- Versions
- 4
- Install Size
- 0 B
- Dist-tags
- 1
- # of Files
- 0
- Maintainers
- 2
- TS Typings
- Yes
destroy 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.
Destroy
Destroy a stream.
This module is meant to ensure a stream gets destroyed, handling different APIs and Node.js bugs.
API
var destroy = require('destroy')
destroy(stream)
Destroy the given stream. In most cases, this is identical to a simple
stream.destroy() call. The rules are as follows for a given stream:
- If the
streamis an instance ofReadStream, then callstream.destroy()and add a listener to theopenevent to callstream.close()if it is fired. This is for a Node.js bug that will leak a file descriptor if.destroy()is called beforeopen. - If the
streamis not an instance ofStream, then nothing happens. - If the
streamhas a.destroy()method, then call it.
The function returns the stream passed in as the argument.
Example
var destroy = require('destroy')
var fs = require('fs')
var stream = fs.createReadStream('package.json')
// ... and later
destroy(stream)
destroy versions
| Version | Published | Tag | Node.js Compatability | Licenses | Dependencies | Direct Vulnerabilities | Publisher |
|---|---|---|---|---|---|---|---|
| 1.0.4 | 16 January 2016 | latest | * | MIT | 0 |
| dougwilson |
| All Versions | |||||||
destroy dependencies
Last updated on
18 January-2021, at 06:06 (UTC).