Is @moveindustries/confidential-asset-wasm-bindings safe to use?

@moveindustries/confidential-asset-wasm-bindings has no known vulnerabilities on the latest version (0.0.4). DepScope rates its health at 47/100 (high risk).

Does @moveindustries/confidential-asset-wasm-bindings have known vulnerabilities?

No known vulnerabilities on the latest version of @moveindustries/confidential-asset-wasm-bindings.

Is @moveindustries/confidential-asset-wasm-bindings deprecated?

No, @moveindustries/confidential-asset-wasm-bindings is actively maintained. Latest release: 0.0.4 (2026-01-30).

What are alternatives to @moveindustries/confidential-asset-wasm-bindings?

Popular alternatives to @moveindustries/confidential-asset-wasm-bindings in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

What license does @moveindustries/confidential-asset-wasm-bindings use?

License information for @moveindustries/confidential-asset-wasm-bindings is not declared in the registry metadata.

@moveindustries/confidential-asset-wasm-bindings

npmv0.0.4

Unified bindings for confidential asset WASM packages

2 versions3 maintainers0 deps33 weekly dl

movementlabsxyz/confidential-asset-wasm-bindings

/ 100

Health

use with caution

@moveindustries/[email protected] low health (47/100) — consider alternatives

Moderate health score (47/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

4/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/@moveindustries/confidential-asset-wasm-bindings