Is @waves/waves-crypto safe to use?

@waves/waves-crypto has no known vulnerabilities on the latest version (3.0.17). DepScope rates its health at 10/100 (critical risk).

What is the latest version of @waves/waves-crypto?

The latest version of @waves/waves-crypto is 3.0.17, released 2019-07-03.

Does @waves/waves-crypto have known vulnerabilities?

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

Is @waves/waves-crypto deprecated?

Yes, @waves/waves-crypto is deprecated: WARNING Library moved to @waves/ts-lib-crypto. Please install new package Consider using ? instead.

What are alternatives to @waves/waves-crypto?

Popular alternatives to @waves/waves-crypto in npm include: ?, minimatch, semver, ansi-styles, debug.

What license does @waves/waves-crypto use?

@waves/waves-crypto is licensed under MIT.

@waves/waves-crypto

npmv3.0.17deprecated

License MITpermissive23 versions2 maintainers1 deps20 weekly dl

wavesplatform/waves-crypto

/ 100

Health

find alternative

@waves/waves-crypto is deprecated — find an alternative

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

3/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (1)

crypto-js

API access

Get this data programmatically — free, no authentication.

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