Is prettify-error safe to use?

prettify-error has 1 known vulnerabilities on the latest version (0.0.1-security). DepScope rates its health at 37/100 (critical risk).

What is the latest version of prettify-error?

The latest version of prettify-error is 0.0.1-security, released 2016-03-23.

Does prettify-error have known vulnerabilities?

Yes. prettify-error has 1 known vulnerabilities. See depscope.dev/pkg/npm/prettify-error for details.

Is prettify-error deprecated?

No, prettify-error is actively maintained. Latest release: 0.0.1-security (2016-03-23).

What are alternatives to prettify-error?

Popular alternatives to prettify-error in npm include: ?, semver, debug, minimatch, ansi-styles.

What license does prettify-error use?

prettify-error is licensed under ISC.

prettify-error

npmv0.0.1-security

This package name is not currently in use, but was formerly occupied by a popular package. To avoid malicious use, npm is hanging on to the package name, but loosely, and we'll probably give it to you if you want it.

License ISCpermissive9 versions1 maintainers0 deps458 weekly dl

npm/security-holder

/ 100

Health

do not use

Do not install. Package is flagged as malicious (advisory MAL-2025-29635).

Health breakdown0 – 100

0/25

maintenance

3/20

popularity

15/25

security

15/15

maturity

4/15

community

Vulnerabilities

1 critical

Advisories (1)

Severity	ID	Summary	Fixed in
critical	MAL-2025-29635	Malicious code in prettify-error (npm)	—

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

⚠ Malicious package

This package is flagged as malicious by the OpenSSF/OSV community feed. Do not install.

Advisory: MAL-2025-29635 — Malicious code in prettify-error (npm)

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/prettify-error