Is @readme/better-ajv-errors safe to use?

@readme/better-ajv-errors has no known vulnerabilities on the latest version (2.4.0). DepScope rates its health at 71/100 (moderate risk).

What is the latest version of @readme/better-ajv-errors?

The latest version of @readme/better-ajv-errors is 2.4.0, released 2025-10-24.

Does @readme/better-ajv-errors have known vulnerabilities?

No known vulnerabilities on the latest version of @readme/better-ajv-errors.

Is @readme/better-ajv-errors deprecated?

No, @readme/better-ajv-errors is actively maintained. Latest release: 2.4.0 (2025-10-24).

What are alternatives to @readme/better-ajv-errors?

Popular alternatives to @readme/better-ajv-errors in npm include: ?, semver, ansi-styles, brace-expansion, ms.

What license does @readme/better-ajv-errors use?

@readme/better-ajv-errors is licensed under Apache-2.0.

@readme/better-ajv-errors

npmv2.4.0

JSON Schema validation for Human

License Apache-2.0permissive26 versions6 maintainers6 deps841,948 weekly dl

readmeio/better-ajv-errors

/ 100

Health

safe to use

@readme/[email protected] is safe to use (health: 71/100)

Health breakdown0 – 100

15/25

maintenance

14/20

popularity

25/25

security

12/15

maturity

5/15

community

0/15

popularity_floor

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (6)

leven picocolors jsonpointer @babel/runtime @babel/code-frame @humanwhocodes/momoa

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@readme/better-ajv-errors