Is wConsequence safe to use?

wConsequence has no known vulnerabilities on the latest version (0.4.520). DepScope rates its health at 48/100 (high risk).

What is the latest version of wConsequence?

The latest version of wConsequence is 0.4.520, released 2022-07-25.

Does wConsequence have known vulnerabilities?

No known vulnerabilities on the latest version of wConsequence.

Is wConsequence deprecated?

No, wConsequence is actively maintained. Latest release: 0.4.520 (2022-07-25).

What are alternatives to wConsequence?

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

What license does wConsequence use?

wConsequence is licensed under MIT.

wConsequence

npmv0.4.520

Advanced synchronization mechanism. Asynchronous routines may use Consequence to wrap postponed result, what allows classify callback for such routines as output, not input, what improves analyzability of a program. Consequence may be used to make a queue

License MITpermissive580 versions1 maintainers5 deps1,239 weekly dl

Wandalen/wConsequence

/ 100

Health

use with caution

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

Moderate health score (48/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

15/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (5)

wTools wProto wprocedure wCopyable wdeasync

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/wConsequence