Is @lukeburns/hypercore-crypto safe to use?

@lukeburns/hypercore-crypto has no known vulnerabilities on the latest version (3.6.6). DepScope rates its health at 54/100 (high risk).

What is the latest version of @lukeburns/hypercore-crypto?

The latest version of @lukeburns/hypercore-crypto is 3.6.6, released 2026-04-24.

Does @lukeburns/hypercore-crypto have known vulnerabilities?

No known vulnerabilities on the latest version of @lukeburns/hypercore-crypto.

Is @lukeburns/hypercore-crypto deprecated?

No, @lukeburns/hypercore-crypto is actively maintained. Latest release: 3.6.6 (2026-04-24).

What are alternatives to @lukeburns/hypercore-crypto?

Popular alternatives to @lukeburns/hypercore-crypto in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @lukeburns/hypercore-crypto use?

@lukeburns/hypercore-crypto is licensed under MIT.

@lukeburns/hypercore-crypto

npmv3.6.6

The crypto primitives used in hypercore, extracted into a separate module

License MITpermissive6 versions1 maintainers4 deps8 weekly dl

mafintosh/hypercore-crypto

/ 100

Health

use with caution

@lukeburns/[email protected] low health (54/100) — consider alternatives

Moderate health score (54/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

53.0 KBminified

16.5 KB gzipped

4 direct dependencies

side effectsscoped

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (4)

@noble/post-quantum b4a compact-encoding sodium-universal

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@lukeburns/hypercore-crypto