Is @mapeo/crypto safe to use?

@mapeo/crypto has no known vulnerabilities on the latest version (1.1.0). DepScope rates its health at 61/100 (moderate risk).

What is the latest version of @mapeo/crypto?

The latest version of @mapeo/crypto is 1.1.0, released 2026-04-22.

Does @mapeo/crypto have known vulnerabilities?

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

Is @mapeo/crypto deprecated?

No, @mapeo/crypto is actively maintained. Latest release: 1.1.0 (2026-04-22).

What are alternatives to @mapeo/crypto?

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

What license does @mapeo/crypto use?

@mapeo/crypto is licensed under MIT.

@mapeo/crypto

npmv1.1.0

Key management and encryption / decryption functions for Mapeo

License MITpermissive13 versions3 maintainers8 deps566 weekly dl

digidem/mapeo-crypto

/ 100

Health

use with caution

@mapeo/[email protected] low health (61/100) — consider alternatives

Moderate health score (61/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

3/20

popularity

25/25

security

9/15

maturity

4/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (8)

base-x base32.js compact-encoding compact-encoding-net compact-encoding-struct crc sodium-universal z32

API access

Get this data programmatically — free, no authentication.

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