Is @oclif/parser safe to use?

@oclif/parser has no known vulnerabilities on the latest version (3.8.17). DepScope rates its health at 21/100 (critical risk).

What is the latest version of @oclif/parser?

The latest version of @oclif/parser is 3.8.17, released 2023-08-19.

Does @oclif/parser have known vulnerabilities?

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

Is @oclif/parser deprecated?

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

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

What license does @oclif/parser use?

@oclif/parser is licensed under MIT.

@oclif/parser

npmv3.8.17deprecated

arg and flag parser for oclif

License MITpermissive44 versions2 maintainers4 deps823,896 weekly dl

oclif/parser

/ 100

Health

find alternative

@oclif/parser is deprecated — find an alternative

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

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

12/15

maturity

0/15

community

Vulnerabilities

none known

Bundle & TypeScript

📦

Bundle Size

104.2 KBminified

32.6 KB gzipped

4 direct dependencies

side effectsscoped

🌟

TypeScript

10/10typed

bundled

Health History

Dependency Tree

License Audit

Dependencies (4)

chalk tslib @oclif/errors @oclif/linewrap

API access

Get this data programmatically — free, no authentication.

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