Is @lit-protocol/crypto safe to use?

@lit-protocol/crypto has no known vulnerabilities on the latest version (8.1.0). DepScope rates its health at 29/100 (critical risk).

What is the latest version of @lit-protocol/crypto?

The latest version of @lit-protocol/crypto is 8.1.0, released 2025-12-22.

Does @lit-protocol/crypto have known vulnerabilities?

No known vulnerabilities on the latest version of @lit-protocol/crypto.

Is @lit-protocol/crypto deprecated?

Yes, @lit-protocol/crypto is deprecated: This package targets a retired Lit Protocol network and is no longer maintained. See https://developer.litprotocol.com for the current SDK. Consider using ? instead.

What are alternatives to @lit-protocol/crypto?

Popular alternatives to @lit-protocol/crypto in npm include: ?, semver, minimatch, ansi-styles, brace-expansion.

What license does @lit-protocol/crypto use?

@lit-protocol/crypto is licensed under MIT.

@lit-protocol/crypto

npmv8.1.0deprecated

The crypto.ts file in the Lit SDK handles cryptographic operations, including the generation, import, encryption and decryption of keys, as well as management of cryptographic shares using BLS and ECDSA schemes.

License MITpermissive612 versions2 maintainers23 deps7,749 weekly dl

LIT-Protocol/js-sdk

/ 100

Health

find alternative

@lit-protocol/crypto is deprecated — find an alternative

Moderate health score (29/100) — verify manually
Package is deprecated

Health breakdown0 – 100

10/25

maintenance

6/20

popularity

25/25

security

15/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@lit-protocol/crypto