Is @blabbing/signals safe to use?

@blabbing/signals has no known vulnerabilities on the latest version (0.0.1). DepScope rates its health at 50/100 (high risk).

What is the latest version of @blabbing/signals?

The latest version of @blabbing/signals is 0.0.1, released 2024-07-28.

Does @blabbing/signals have known vulnerabilities?

No known vulnerabilities on the latest version of @blabbing/signals.

Is @blabbing/signals deprecated?

No, @blabbing/signals is actively maintained. Latest release: 0.0.1 (2024-07-28).

What are alternatives to @blabbing/signals?

Popular alternatives to @blabbing/signals in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @blabbing/signals use?

@blabbing/signals is licensed under MIT.

@blabbing/signals

npmv0.0.1

A reactive state management tool

License MITpermissive266 versions1 maintainers1 deps560 weekly dl

/ 100

Health

use with caution

@blabbing/[email protected] low health (50/100) — consider alternatives

Moderate health score (50/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

3/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

8.4 KBminified

2.7 KB gzipped

1 direct dependencies

side effectsscoped

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (1)

signal-polyfill

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@blabbing/signals