Is crypto-timing-safe-equals safe to use?

crypto-timing-safe-equals has no known vulnerabilities on the latest version (1.0.1). DepScope rates its health at 33/100 (critical risk).

What is the latest version of crypto-timing-safe-equals?

The latest version of crypto-timing-safe-equals is 1.0.1, released 2025-01-17.

No known vulnerabilities on the latest version of crypto-timing-safe-equals.

No, crypto-timing-safe-equals is actively maintained. Latest release: 1.0.1 (2025-01-17).

Popular alternatives to crypto-timing-safe-equals in npm include: semver, debug, ansi-styles, minimatch, brace-expansion.

crypto-timing-safe-equals is licensed under MIT.

npmv1.0.1

An isomorphic timing-safe equality function for strings and Uint8Arrays.

License MITpermissive2 versions1 maintainers0 deps72 weekly dl

33

/ 100

Health

use with caution

[email protected] low health (33/100) — consider alternatives

Moderate health score (33/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

0

none known

🌟

10/10typed

bundled

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/crypto-timing-safe-equals