Is @oclif/errors safe to use?

@oclif/errors has no known vulnerabilities on the latest version (1.3.6). DepScope rates its health at 24/100 (critical risk).

What is the latest version of @oclif/errors?

The latest version of @oclif/errors is 1.3.6, released 2022-09-27.

Does @oclif/errors have known vulnerabilities?

No known vulnerabilities on the latest version of @oclif/errors.

Is @oclif/errors deprecated?

Yes, @oclif/errors is deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. Consider using ? instead.

What are alternatives to @oclif/errors?

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

What license does @oclif/errors use?

@oclif/errors is licensed under MIT.

@oclif/errors

npmv1.3.6deprecated

display friendly CLI errors and log to error log

License MITpermissive28 versions2 maintainers5 deps1,480,530 weekly dl

oclif/errors

/ 100

Health

find alternative

@oclif/errors is deprecated — find an alternative

Moderate health score (24/100) — verify manually
Package is deprecated

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

12/15

maturity

0/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

10/10typed

bundled

Quality signals

Publish security

npm signed

Health History

Dependency Tree

License Audit

Dependencies (5)

fs-extra wrap-ansi strip-ansi clean-stack indent-string

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@oclif/errors