Is @pnpm/crypto.base32-hash safe to use?

@pnpm/crypto.base32-hash has no known vulnerabilities on the latest version (900.0.0). DepScope rates its health at 82/100 (low risk).

What is the latest version of @pnpm/crypto.base32-hash?

The latest version of @pnpm/crypto.base32-hash is 900.0.0, released 2024-11-28.

Does @pnpm/crypto.base32-hash have known vulnerabilities?

No known vulnerabilities on the latest version of @pnpm/crypto.base32-hash.

Is @pnpm/crypto.base32-hash deprecated?

No, @pnpm/crypto.base32-hash is actively maintained. Latest release: 900.0.0 (2024-11-28).

What are alternatives to @pnpm/crypto.base32-hash?

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

What license does @pnpm/crypto.base32-hash use?

@pnpm/crypto.base32-hash is licensed under MIT.

@pnpm/crypto.base32-hash

npmv900.0.0

Create a base32 hash

License MITpermissive6 versions2 maintainers2 deps2,211,808 weekly dl

pnpm/pnpm

/ 100

Health

safe to use

@pnpm/[email protected] is safe to use (health: 82/100)

Health breakdown0 – 100

20/25

maintenance

17/20

popularity

25/25

security

9/15

maturity

11/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Quality signals

OSS Criticality

0.63high

Health History

Dependency Tree

License Audit

Dependencies (2)

rfc4648 @pnpm/crypto.polyfill

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@pnpm/crypto.base32-hash