get-port-cli

v2.0.0

Get an available port

MIT
Latest version published 2 years ago
    npm install get-port-cli
  
We couldn't find any similar packages Browse all packages

Package Health Score

47 / 100
Make sure the open source you're using is safe to use
Secure my Project

Popularity

Recognized

Weekly Downloads (28,388)

Dependents
43
GitHub Stars
102
Forks
8
Contributors
3

The npm package get-port-cli receives a total of 28,388 downloads a week. As such, we scored get-port-cli popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package get-port-cli, we found that it has been starred 102 times, and that 43 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

Direct Vulnerabilities

1.0.0
1.1.0
2.0.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.0.0
1.1.0
2.0.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

1.0.0
1.1.0
2.0.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 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 get-port-cli 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 && snyk test get-port-cli
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

Open Issues
0
Merged PR
2
Open PR
0
Last Commit
2 months ago

Further analysis of the maintenance status of get-port-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 get-port-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
Yes
Contributors
3
Funding
Yes

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 47/100 package health 47/100

Package

Node.js Compatibility
>=8

Age
5 years
Dependencies
2 Direct
Versions
4
Install Size
3.35 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
No

get-port-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.