cli

v1.0.1

A tool for rapidly building command line apps

MIT
Latest version published about 4 years ago
    npm install cli
  

Package Health Score

60 / 100
  • Popularity
    Popular
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Sustainable

Popularity

Popular
Weekly Downloads (581,820)
Dependents
765
GitHub Stars
778
Forks
75
Contributors
20

The npm package cli receives a total of 581,820 downloads a week. As such, we scored cli popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package cli, we found that it has been starred 778 times, and that 765 other projects on 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

No known security issues

Security and license risk for recent versions


Direct Vulnerabilities

0.11.1
0.11.2
0.11.3
1.0.0
1.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.11.1
0.11.2
0.11.3
1.0.0
1.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.11.1
0.11.2
0.11.3
1.0.0
1.0.1
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Security Policy
No
All security vulnerabilities belong to production dependencies of direct and indirect packages.

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

We found a way for you to contribute to the project! Looks like cli is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test cli
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
17
Merged PR
29
Open PR
11
Last Commit
4 years ago

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

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No
License
MIT

With more than 10 contributors for the cli 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 cli is missing a Code of Conduct.

Package

Node.js Compatibility
>=0.2.5

Age
10 years
Dependencies
2 Direct / 12 Total
Versions
5
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
Yes

We detected a total of 12 direct & transitive dependencies for cli. See the full dependency tree of cli

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