node-vagrant

v1.5.0

Node js wrapper for vagrant CLI - command line tool.

ISC
Latest version published 1 year ago
    npm install node-vagrant
  

Package Health Score

43 / 100

Popularity

Limited

Weekly Downloads (29)

Download trend
Dependents
0
GitHub Stars
29
Forks
17
Contributors
20

Direct Usage Popularity


The npm package node-vagrant receives a total of 29 downloads a week. As such, we scored node-vagrant popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package node-vagrant, we found that it has been starred 29 times, and that 0 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

08/2017
01/2018
08/2019
08/2019
12/2020

Direct Vulnerabilities

1.1.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.2.2
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.3.10
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.4.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.5.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular

License Risk

1.1.0
  • 0
    H
  • 0
    M
  • 0
    L
1.2.2
  • 0
    H
  • 0
    M
  • 0
    L
1.3.10
  • 0
    H
  • 0
    M
  • 0
    L
1.4.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.5.0
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
ISC

Security Policy
No

We found a way for you to contribute to the project! Looks like node-vagrant 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 node-vagrant
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
2
Last Release
1 year ago
Last Commit
1 year ago

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

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
20
Funding
No

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


Embed Package Health Score Badge

package health: 43/100 package health 43/100

Package

Node.js Compatibility
not defined

Age
7 years
Dependencies
1 Direct
Versions
23
Install Size
84.1 kB
Dist-tags
1
# of Files
38
Maintainers
1
TS Typings
Yes

node-vagrant 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.