View @oclif/config on Snyk Open Source Advisor

Package Health Score

55 / 100

security
No known security issues
popularity
Influential project
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

All Versions

Version			Vulnerabilities	License Risk
1.18.17	\|	08/2023	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.17.1	\|	11/2021	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.17.0	\|	08/2020	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.16.0	\|	06/2020	0 C 0 H 0 M 0 L	0 H 0 M 0 L
1.15.1	\|	04/2020	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

Influential project

Weekly Downloads (1,445,627)

GitHub Stars: 25
Forks: 36
Contributors: 30

Direct Usage Popularity

The npm package @oclif/config receives a total of 1,445,627 downloads a week. As such, we scored @oclif/config popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package @oclif/config, we found that it has been starred 25 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/config 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/config is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Inactive

deprecated

Commit Frequency

No Recent Commits

Open Issues: 14
Open PR: 10
Last Release: 1 year ago
Last Commit: 1 year ago

Further analysis of the maintenance status of @oclif/config 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/config 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: 6 Direct
Versions: 132
Install Size: 55.3 kB
Dist-tags: 1
# of Files: 27
Maintainers: 3
TS Typings: Yes

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

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

adobe / aio-cli / src / index.js View on Github

AIOCommand.run = async (argv, opts) =&gt; {
  if (!argv) {
    argv = process.argv.slice(2)
  }

  // oclif originally included the following too ...
  // this resulted in an uncovered line in the tests, and it appeared to never happen anyway
  // seem like it would only
  // ||  module.parent &amp;&amp; module.parent.parent &amp;&amp; module.parent.parent.filename
  const config = await Config.load(opts || __dirname)

  let subCommand = argv[0]

  // 1. find the first flag ( note: there could be none ... )
  let firstFlag = argv.slice().findIndex(elem =&gt; elem.indexOf('-') === 0)
  if (firstFlag &lt; 0) {
    firstFlag = argv.length
  }
  // 2. try to make the biggest topic command by combining with ':'
  // and looking up in this.config.commandIDs
  for (let x = firstFlag; x &gt; -1; x--) {
    subCommand = argv.slice(0, x).join(':')
    // if (config.findTopic(subCommand)) { // &lt;= this works but does not support aliases
    if (config.findCommand(subCommand)) {
      argv = [subCommand].concat(argv.slice(x))
      break

View more ways to use @oclif/config

@oclif/config dependencies

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

@oclif/config development dependencies

@types/chai @types/indent-string @types/lodash @types/mocha @types/node @types/proxyquire @types/wrap-ansi chai conventional-changelog-cli eslint eslint-config-oclif eslint-config-oclif-typescript fancy-test lodash mocha proxyquire ts-node typescript

FAQs

What is @oclif/config?

base config object and standard interfaces for oclif components. Visit Snyk Advisor to see a full health score report for @oclif/config, including popularity, security, maintenance & community analysis.

Is @oclif/config popular?

The npm package @oclif/config receives a total of 1,445,627 weekly downloads. As such, @oclif/config popularity was classified as an influential project. Visit the popularity section on Snyk Advisor to see the full health analysis.

Is @oclif/config well maintained?

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

Is @oclif/config safe to use?

The npm package @oclif/config 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 5 November-2024, at 08:01 (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/config

base config object and standard interfaces for oclif components 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 (1,445,627)

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/config?

@oclif/config

@oclif/config dependencies

@oclif/config development dependencies

FAQs

What is @oclif/config?

Is @oclif/config popular?

Is @oclif/config well maintained?

Is @oclif/config 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 (1,445,627)

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/config?

@oclif/config

@oclif/config dependencies

@oclif/config development dependencies

FAQs

What is @oclif/config?

Is @oclif/config popular?

Is @oclif/config well maintained?

Is @oclif/config 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