1. Advisor
  2. JavaScript packages
  3. whyargs

whyargs

v17.4.0

yargs the modern, pirate-themed, successor to optimist. For more information about how to use this package see README

Latest version published 3 years ago
License: MIT
NPM
GitHub

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

59 / 100

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
17.4.0 | 03/2022
Popular
  • 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 (0)

Download trend
GitHub Stars
11.06K
Forks
994
Contributors
270

Direct Usage Popularity

The npm package whyargs receives a total of 0 downloads a week. As such, we scored whyargs popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package whyargs, we found that it has been starred 11,061 times.

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

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
Yes
Contributors
270
Funding
No

A good and healthy external contribution signal for whyargs project, which invites more than one hundred open source maintainers to collaborate on the repository.

Embed Package Health Score Badge

package health: 59/100 package health 59/100

Maintenance

Inactive

Commit Frequency

Open Issues
294
Open PR
26
Last Release
3 years ago
Last Commit
11 months ago

Further analysis of the maintenance status of whyargs 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 whyargs 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

scan-reversed

Check your package.json

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

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
>=12
Age
3 years
Dependencies
7 Direct
Versions
2
Install Size
283 kB
Dist-tags
1
# of Files
59
Maintainers
1
TS Typings
No

whyargs 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.