@oclif/plugin-legacy

v2.0.18

converts older style plugins to be compatible with oclif For more information about how to use this package see README

Latest version published 2 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

76 / 100

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
2.0.18 | 09/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.6 | 10/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.8 | 02/2018
  • 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

Small

Weekly Downloads (8,966)

Download trend
GitHub Stars
3
Forks
1
Contributors
20

Direct Usage Popularity

TOP 10%

The npm package @oclif/plugin-legacy receives a total of 8,966 downloads a week. As such, we scored @oclif/plugin-legacy popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package @oclif/plugin-legacy, we found that it has been starred 3 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
20
Funding
No

With more than 10 contributors for the @oclif/plugin-legacy 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/plugin-legacy is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 76/100 package health 76/100

Maintenance

Healthy

Commit Frequency

Open Issues
0
Open PR
0
Last Release
2 months ago
Last Commit
5 days ago

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

We found that @oclif/plugin-legacy demonstrates a positive version release cadence with at least one new version released in the past 3 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
>=8.0.0

Age
7 years
Dependencies
5 Direct
Versions
64
Install Size
368 kB
Dist-tags
2
# of Files
11
Maintainers
3
TS Typings
Yes

@oclif/plugin-legacy 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.