@oclif/plugin-legacy

v1.2.4

converts older style plugins to be compatible with oclif

MIT
Latest version published 7 days ago
    npm install @oclif/plugin-legacy
  

Package Health Score

75 / 100

Popularity

Recognized

Weekly Downloads (24,300)

Download trend
Dependents
95
GitHub Stars
1
Forks
0
Contributors
20

Direct Usage Popularity

Uncommon

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

Based on project statistics from the GitHub repository for the npm package @oclif/plugin-legacy, we found that it has been starred 1 times, and that 95 other projects in the ecosystem are dependent on it.

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

Security

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

02/2018
02/2019
02/2021
12/2021

Direct Vulnerabilities

0.1.8
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.1.4
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.2.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.2.4
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.1.8
1.1.4
Popular
1.2.0
1.2.4
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

0.1.8
  • 0
    H
  • 0
    M
  • 0
    L
1.1.4
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.2.0
  • 0
    H
  • 0
    M
  • 0
    L
1.2.4
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like @oclif/plugin-legacy is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test @oclif/plugin-legacy
Keep your project free of vulnerabilities with Snyk

Maintenance

Healthy

Commit Frequency

Open Issues
0
Open PR
20
Last Release
7 days ago
Last Commit
7 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.

Community

Sustainable
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: 75/100 package health 75/100

Package

Node.js Compatibility
>=8.0.0

Age
4 years
Dependencies
7 Direct
Versions
33
Install Size
12.9 kB
Dist-tags
1
# of Files
10
Maintainers
8
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.