Package Health Score

71 / 100

security
No known security issues
popularity
Influential project
maintenance
Sustainable
community
Limited

Explore Similar Packages

Security

No known security issues

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

Security and license risk for significant versions

Version				Vulnerabilities	License Risk
1.2.0	\|	03/2022	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.1.1	\|	02/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.0.4	\|	01/2016		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

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 (30,785,043)

GitHub Stars: 56
Forks: 9
Contributors: 3

Direct Usage Popularity

The npm package destroy receives a total of 30,785,043 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 56 times.

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: 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.

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

No Recent Commits

Open Issues: 0
Open PR: 0
Last Release: 2 years ago
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 Sustainable.

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.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >= 0.8

Age: 10 years
Dependencies: 0 Direct
Versions: 7
Install Size: 9.02 kB
Dist-tags: 1
# of Files: 4
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.

Not sure how to use destroy?

To help you get started, we've collected the most common ways that destroy is being used within popular public projects.

physiii / open-automation / node_modules / koa / lib / response.js View on Github

if ('string' == typeof val) {
      if (setType) this.type = /^\s* this.ctx.onerror(err));

      // overwriting
      if (null != original &amp;&amp; original != val) this.remove('Content-Length');

      if (setType) this.type = 'bin';
      return;
    }

    // json
    this.remove('Content-Length');
    this.type = 'json';
  },

View more ways to use destroy

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 [, suppress])

Destroy the given stream, and optionally suppress any future error events.

In most cases, this is identical to a simple stream.destroy() call. The rules are as follows for a given stream:

If the stream is an instance of ReadStream, then call stream.destroy() and add a listener to the open event to call stream.close() if it is fired. This is for a Node.js bug that will leak a file descriptor if .destroy() is called before open.
If the stream is an instance of a zlib stream, then call stream.destroy() and close the underlying zlib handle if open, otherwise call stream.close(). This is for consistency across Node.js versions and a Node.js bug that will leak a native zlib handle.
If the stream is not an instance of Stream, then nothing happens.
If the stream has 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 development dependencies

eslint eslint-config-standard eslint-plugin-import eslint-plugin-node eslint-plugin-promise eslint-plugin-standard mocha nyc

FAQs

What is destroy?

destroy a stream if possible. Visit Snyk Advisor to see a full health score report for destroy, including popularity, security, maintenance & community analysis.

Is destroy popular?

The npm package destroy receives a total of 30,785,043 weekly downloads. As such, destroy popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is destroy well maintained?

We found indications that destroy maintenance is sustainable demonstrating some project activity. We saw a total of 3 open source contributors collaborating on the project. See the full package health analysis to learn more about the package maintenance status.

Is destroy safe to use?

The npm package destroy was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 30 September-2023, at 17:18 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

destroy

destroy a stream if possible For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (30,785,043)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use destroy?

destroy

API

destroy(stream [, suppress])

Example

destroy development dependencies

FAQs

What is destroy?

Is destroy popular?

Is destroy well maintained?

Is destroy safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (30,785,043)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use destroy?

destroy

API

destroy(stream [, suppress])

Example

destroy development dependencies

FAQs

What is destroy?

Is destroy popular?

Is destroy well maintained?

Is destroy safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues