@oclif/config

v1.18.17

base config object and standard interfaces for oclif components For more information about how to use this package see README

Latest version published 9 months ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

49 / 100

Security

Security review needed
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.18.16 | 07/2023
Popular
  • 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.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
No

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,519,560)

Download trend
GitHub Stars
24
Forks
36
Contributors
30

Direct Usage Popularity

TOP 5%

The npm package @oclif/config receives a total of 1,519,560 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 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/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

package health: 49/100 package health 49/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
14
Open PR
10
Last Release
9 months ago
Last Commit
9 months 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.

We found that @oclif/config demonstrates a positive version release cadence with at least one new version released in the past 12 months.

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

Package

Node.js Compatibility
>=8.0.0

Age
6 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.