Is @automerge/automerge-wasm safe to use?

@automerge/automerge-wasm has no known vulnerabilities on the latest version (1.0.0-preview.0). DepScope rates its health at 56/100 (high risk).

What is the latest version of @automerge/automerge-wasm?

The latest version of @automerge/automerge-wasm is 1.0.0-preview.0, released 2025-01-17.

Does @automerge/automerge-wasm have known vulnerabilities?

No known vulnerabilities on the latest version of @automerge/automerge-wasm.

Is @automerge/automerge-wasm deprecated?

No, @automerge/automerge-wasm is actively maintained. Latest release: 1.0.0-preview.0 (2025-01-17).

What are alternatives to @automerge/automerge-wasm?

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

What license does @automerge/automerge-wasm use?

@automerge/automerge-wasm is licensed under MIT.

@automerge/automerge-wasm

npmv1.0.0-preview.0

wasm-bindgen bindings to the automerge rust implementation

License MITpermissive56 versions6 maintainers0 deps1,031 weekly dl

automerge/automerge

/ 100

Health

safe to use

@automerge/[email protected] is safe to use (health: 56/100)

Health breakdown0 – 100

5/25

maintenance

6/20

popularity

25/25

security

15/15

maturity

5/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/@automerge/automerge-wasm