Is hypercore-id-encoding safe to use?

hypercore-id-encoding has no known vulnerabilities on the latest version (1.3.0). DepScope rates its health at 37/100 (critical risk).

What is the latest version of hypercore-id-encoding?

The latest version of hypercore-id-encoding is 1.3.0, released 2024-03-26.

Does hypercore-id-encoding have known vulnerabilities?

No known vulnerabilities on the latest version of hypercore-id-encoding.

Is hypercore-id-encoding deprecated?

No, hypercore-id-encoding is actively maintained. Latest release: 1.3.0 (2024-03-26).

What are alternatives to hypercore-id-encoding?

Popular alternatives to hypercore-id-encoding in npm include: minimatch, commander, eslint-visitor-keys, ajv, color-name.

What license does hypercore-id-encoding use?

hypercore-id-encoding is licensed under Apache-2.0.

hypercore-id-encoding

npmv1.3.0

Convert Hypercore keys to/from z-base32 or hex

License Apache-2.0permissive6 versions2 maintainers2 deps

holepunchto/hypercore-id-encoding

/ 100

Health

use with caution

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

Low health score (37/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

12.1 KBminified

3.6 KB gzipped

2 direct dependencies

side effects

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (2)

b4a z32

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/hypercore-id-encoding