Is @automerge/automerge-repo safe to use?

@automerge/automerge-repo has no known vulnerabilities on the latest version (2.5.6). DepScope rates its health at 75/100 (moderate risk).

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

The latest version of @automerge/automerge-repo is 2.5.6, released 2026-05-18.

Does @automerge/automerge-repo have known vulnerabilities?

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

Is @automerge/automerge-repo deprecated?

No, @automerge/automerge-repo is actively maintained. Latest release: 2.5.6 (2026-05-18).

What are alternatives to @automerge/automerge-repo?

Popular alternatives to @automerge/automerge-repo in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @automerge/automerge-repo use?

@automerge/automerge-repo is licensed under MIT.

@automerge/automerge-repo

npmv2.5.6

A repository object to manage a collection of automerge documents

License MITpermissive152 versions6 maintainers8 deps19,845 weekly dl

automerge/automerge-repo

/ 100

Health

safe to use

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

Health breakdown0 – 100

20/25

maintenance

10/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

Dependencies (8)

uuid debug cbor-x xstate bs58check fast-sha256 eventemitter3 @automerge/automerge

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@automerge/automerge-repo