Package Health Score

53 / 100

security
No known security issues
popularity
Popular
maintenance
Inactive
community
Limited

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

Version			Vulnerabilities	License Risk
3.8.17	\|	08/2023	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.7.3	\|	03/2019	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.6.3	\|	10/2018	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.5.3	\|	06/2018	0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.4.1	\|	05/2018	0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

MIT

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Popular

Weekly Downloads (672,475)

GitHub Stars: 24
Forks: 23
Contributors: 30

Direct Usage Popularity

The npm package @oclif/parser receives a total of 672,475 downloads a week. As such, we scored @oclif/parser popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package @oclif/parser, we found that it has been starred 24 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 30
Funding: No

With more than 10 contributors for the @oclif/parser repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like @oclif/parser is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

deprecated

Commit Frequency

No Recent Commits

Open Issues: 13
Open PR: 8
Last Release: 1 year ago
Last Commit: 1 year ago

Further analysis of the maintenance status of @oclif/parser based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for @oclif/parser is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=8.0.0

Age: 7 years
Dependencies: 4 Direct
Versions: 45
Install Size: 36.3 kB
Dist-tags: 1
# of Files: 29
Maintainers: 2
TS Typings: Yes

@oclif/parser has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use @oclif/parser?

To help you get started, we've collected the most common ways that @oclif/parser is being used within popular public projects.

oclif / command / src / flags.ts View on Github

export const version = (opts: Partial&gt; = {}) =&gt; {
  return Parser.flags.boolean({
    // char: 'v',
    description: 'show CLI version',
    ...opts,
    parse: (_: any, cmd: Command) =&gt; {
      cmd.log(cmd.config.userAgent)
      cmd.exit(0)
    },
  })
}
export const help = (opts: Partial&gt; = {}) =&gt; {

View more ways to use @oclif/parser

@oclif/parser

This library has been replaced by @oclif/core and is now in maintenance mode. We will only consider PRs that address security concerns.

arg and flag parser for oclif

CLI flag parser.

Usage:

const CLI = require('cli-flags')

const {flags, args} = CLI.parse({
  flags: {
    'output-file': CLI.flags.string({char: 'o'}),
    force: CLI.flags.boolean({char: 'f'})
  },
  args: [
    {name: 'input', required: true}
  ]
})

if (flags.force) {
  console.log('--force was set')
}

if (flags['output-file']) {
  console.log(`output file is: ${flags['output-file']}`)
}

console.log(`input arg: ${args.input}`)

// $ node example.js -f myinput --output-file=myexample.txt
// --force was set
// output file is: myexample.txt
// input arg: myinput

@oclif/parser dependencies

@oclif/errors @oclif/linewrap chalk tslib

@oclif/parser development dependencies

@types/chai @types/mocha @types/nock @types/node @types/node-notifier @types/read-pkg chai conventional-changelog-cli eslint eslint-config-oclif eslint-config-oclif-typescript mocha ts-node typescript

FAQs

What is @oclif/parser?

arg and flag parser for oclif. Visit Snyk Advisor to see a full health score report for @oclif/parser, including popularity, security, maintenance & community analysis.

Is @oclif/parser popular?

The npm package @oclif/parser receives a total of 672,475 weekly downloads. As such, @oclif/parser popularity was classified as a popular. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @oclif/parser well maintained?

We found indications that @oclif/parser is an Inactive project. See the full package health analysis to learn more about the package maintenance status.

Is @oclif/parser safe to use?

The npm package @oclif/parser was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use. See the full health analysis review.

Last updated on 3 November-2024, at 03:14 (UTC).

Build a secure application checklist

Select a recommended open source package

Minimize your risk by selecting secure & well maintained open source packages

DONE

Scan your app for vulnerabilities

Scan your application to find vulnerabilities in your: source code, open source dependencies, containers and configuration files

SCAN NOW

Fix identified vulnerabilities

Easily fix your code by leveraging automatically generated PRs

AUTO FIX

Monitor for new issues

New vulnerabilities are discovered every day. Get notified if your application is affected

MONITOR APP

@oclif/parser

arg and flag parser for oclif For more information about how to use this package see README

Ensure you're using the healthiest npm packages

Package Health Score

Explore Similar Packages

Security

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Popularity

Weekly Downloads (672,475)

Direct Usage Popularity

Community

Embed Package Health Score Badge

Maintenance

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Package

Not sure how to use @oclif/parser?

@oclif/parser

@oclif/parser dependencies

@oclif/parser development dependencies

FAQs

What is @oclif/parser?

Is @oclif/parser popular?

Is @oclif/parser well maintained?

Is @oclif/parser safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Fix identified vulnerabilities

Monitor for new issues

Package Health Score

Explore Similar Packages

Security and license risk for significant versions

Is your project affected by vulnerabilities?

Weekly Downloads (672,475)

Direct Usage Popularity

Embed Package Health Score Badge

Commit Frequency

Keep your project healthy

Check your package.json

Snyk Vulnerability Scanner

Not sure how to use @oclif/parser?

@oclif/parser

@oclif/parser dependencies

@oclif/parser development dependencies

FAQs

What is @oclif/parser?

Is @oclif/parser popular?

Is @oclif/parser well maintained?

Is @oclif/parser safe to use?

Build a secure application checklist

Select a recommended open source package

Scan your app for vulnerabilities

Source Code

Open Source

Container

Config

Fix identified vulnerabilities

Monitor for new issues