Is stream-to-promise safe to use?

stream-to-promise has no known vulnerabilities on the latest version (3.0.0). DepScope rates its health at 42/100 (high risk).

What is the latest version of stream-to-promise?

The latest version of stream-to-promise is 3.0.0, released 2020-05-25.

Does stream-to-promise have known vulnerabilities?

No known vulnerabilities on the latest version of stream-to-promise.

Is stream-to-promise deprecated?

No, stream-to-promise is actively maintained. Latest release: 3.0.0 (2020-05-25).

What are alternatives to stream-to-promise?

Popular alternatives to stream-to-promise in npm include: semver, debug, ansi-styles, minimatch, strip-ansi.

What license does stream-to-promise use?

stream-to-promise is licensed under MIT.

stream-to-promise

npmv3.0.0

Convert streams (readable or writable) to promises

License MITpermissive18 versions1 maintainers3 deps

git://github.com/bendrucker/stream-to-promise

/ 100

Health

safe to use

[email protected] is safe to use (health: 42/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

7/10typed

Types from @types/stream-to-promise (DefinitelyTyped)

Quality signals

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (3)

any-promise end-of-stream stream-to-array

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/stream-to-promise