destroy

v1.0.4

destroy a stream if possible

MIT
Latest version published 5 years ago
    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 use
Secure my Project

Popularity

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
Powered by Snyk

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

1.0.4
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.0.4
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

1.0.4
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

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
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive
Commit Frequency
No Recent Commits
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 health: 53/100 package health 53/100

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.