Is callbag-for-each safe to use?

callbag-for-each has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 40/100 (high risk).

What is the latest version of callbag-for-each?

The latest version of callbag-for-each is 1.1.0, released 2018-08-30.

Does callbag-for-each have known vulnerabilities?

No known vulnerabilities on the latest version of callbag-for-each.

Is callbag-for-each deprecated?

No, callbag-for-each is actively maintained. Latest release: 1.1.0 (2018-08-30).

What are alternatives to callbag-for-each?

Popular alternatives to callbag-for-each in npm include: semver, ansi-styles, minimatch, debug, brace-expansion.

What license does callbag-for-each use?

callbag-for-each is licensed under MIT.

callbag-for-each

npmv1.1.0

Callbag sink that consume both pullable and listenable sources

License MITpermissive3 versions2 maintainers1 deps

staltz/callbag-for-each

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (1)

callbag

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/callbag-for-each