Is @shelby-protocol/clay-codes safe to use?

@shelby-protocol/clay-codes has no known vulnerabilities on the latest version (0.0.2). DepScope rates its health at 51/100 (high risk).

What is the latest version of @shelby-protocol/clay-codes?

The latest version of @shelby-protocol/clay-codes is 0.0.2, released 2025-12-13.

Does @shelby-protocol/clay-codes have known vulnerabilities?

No known vulnerabilities on the latest version of @shelby-protocol/clay-codes.

Is @shelby-protocol/clay-codes deprecated?

No, @shelby-protocol/clay-codes is actively maintained. Latest release: 0.0.2 (2025-12-13).

What are alternatives to @shelby-protocol/clay-codes?

Popular alternatives to @shelby-protocol/clay-codes in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @shelby-protocol/clay-codes use?

License information for @shelby-protocol/clay-codes is not declared in the registry metadata.

@shelby-protocol/clay-codes

npmv0.0.2

WebAssembly bindings for Clay codes, a class of regenerating codes for distributed storage.

3 versions1 maintainers0 deps1,217 weekly dl

/ 100

Health

use with caution

@shelby-protocol/[email protected] low health (51/100) — consider alternatives

Moderate health score (51/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

6/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@shelby-protocol/clay-codes