Is @counterplay/warlock safe to use?

@counterplay/warlock has no known vulnerabilities on the latest version (0.3.1). DepScope rates its health at 45/100 (high risk).

What is the latest version of @counterplay/warlock?

The latest version of @counterplay/warlock is 0.3.1, released 2016-01-30.

Does @counterplay/warlock have known vulnerabilities?

No known vulnerabilities on the latest version of @counterplay/warlock.

Is @counterplay/warlock deprecated?

No, @counterplay/warlock is actively maintained. Latest release: 0.3.1 (2016-01-30).

What are alternatives to @counterplay/warlock?

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

What license does @counterplay/warlock use?

License information for @counterplay/warlock is not declared in the registry metadata.

@counterplay/warlock

npmv0.3.1

Battle-hardened distributed locking using redis

2 versions12 maintainers2 deps4 weekly dl

marwanhilmi/warlock

/ 100

Health

use with caution

@counterplay/[email protected] low health (45/100) — consider alternatives

Moderate health score (45/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

15/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

9.7 KBminified

3.5 KB gzipped

2 direct dependencies

side effectsscoped

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

uuid node-redis-scripty

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@counterplay/warlock