Is @originjs/crypto-js-wasm safe to use?

@originjs/crypto-js-wasm has no known vulnerabilities on the latest version (1.1.1). DepScope rates its health at 42/100 (high risk).

What is the latest version of @originjs/crypto-js-wasm?

The latest version of @originjs/crypto-js-wasm is 1.1.1, released 2024-06-25.

Does @originjs/crypto-js-wasm have known vulnerabilities?

No known vulnerabilities on the latest version of @originjs/crypto-js-wasm.

Is @originjs/crypto-js-wasm deprecated?

No, @originjs/crypto-js-wasm is actively maintained. Latest release: 1.1.1 (2024-06-25).

What are alternatives to @originjs/crypto-js-wasm?

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

What license does @originjs/crypto-js-wasm use?

@originjs/crypto-js-wasm is licensed under MulanPSL2.

@originjs/crypto-js-wasm

npmv1.1.1

An alternative to crypto-js implemented with WebAssembly and ESM

License MulanPSL28 versions6 maintainers3 deps181 weekly dl

originjs/crypto-js-wasm

/ 100

Health

use with caution

@originjs/[email protected] low health (42/100) — consider alternatives

Moderate health score (42/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

25/25

security

9/15

maturity

5/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (3)

add pako global

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@originjs/crypto-js-wasm