Is stream-to-buffer safe to use?

stream-to-buffer has no known vulnerabilities on the latest version (0.1.0). DepScope rates its health at 57/100 (high risk).

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

The latest version of stream-to-buffer is 0.1.0, released 2013-10-02.

Does stream-to-buffer have known vulnerabilities?

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

Is stream-to-buffer deprecated?

No, stream-to-buffer is actively maintained. Latest release: 0.1.0 (2013-10-02).

What are alternatives to stream-to-buffer?

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

What license does stream-to-buffer use?

License information for stream-to-buffer is not declared in the registry metadata.

stream-to-buffer

npmv0.1.0

Concatenate a readable stream's data into a single buffer

2 versions2 maintainers1 deps158,219 weekly dl

jonathanong/stream-to-buffer

/ 100

Health

use with caution

[email protected] low health (57/100) — consider alternatives

Moderate health score (57/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

15/15

maturity

3/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

stream-to

API access

Get this data programmatically — free, no authentication.

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