Is stream-to-observable safe to use?

stream-to-observable has no known vulnerabilities on the latest version (0.2.0). DepScope rates its health at 56/100 (high risk).

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

The latest version of stream-to-observable is 0.2.0, released 2016-06-29.

Does stream-to-observable have known vulnerabilities?

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

Is stream-to-observable deprecated?

No, stream-to-observable is actively maintained. Latest release: 0.2.0 (2016-06-29).

What are alternatives to stream-to-observable?

Popular alternatives to stream-to-observable in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does stream-to-observable use?

stream-to-observable is licensed under MIT.

stream-to-observable

npmv0.2.0

Convert Node Streams into ECMAScript-Observables

License MITpermissive3 versions1 maintainers1 deps177,106 weekly dl

jamestalmage/stream-to-observable

/ 100

Health

use with caution

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

Moderate health score (56/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

15/15

maturity

2/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

1.7 KBminified

0.9 KB gzipped

1 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

any-observable

API access

Get this data programmatically — free, no authentication.

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