Is @oclif/config safe to use?

@oclif/config has no known vulnerabilities on the latest version (1.18.17). DepScope rates its health at 27/100 (critical risk).

What is the latest version of @oclif/config?

The latest version of @oclif/config is 1.18.17, released 2023-08-20.

Does @oclif/config have known vulnerabilities?

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

Is @oclif/config deprecated?

Yes, @oclif/config 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/config?

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

What license does @oclif/config use?

@oclif/config is licensed under MIT.

@oclif/config

npmv1.18.17deprecated

base config object and standard interfaces for oclif components

License MITpermissive131 versions3 maintainers6 deps2,048,658 weekly dl

oclif/config

/ 100

Health

find alternative

@oclif/config is deprecated — find an alternative

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

Health breakdown0 – 100

0/25

maintenance

17/20

popularity

25/25

security

15/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 (6)

debug tslib globby is-wsl @oclif/errors @oclif/parser

API access

Get this data programmatically — free, no authentication.

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