1. Advisor
  2. JavaScript packages
  3. control

control

v0.2.3

Scripted asynchronous control of remote machines in parallel via ssh For more information about how to use this package see README

Latest version published 14 years ago
License: Unknown
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

39 / 100

Explore Similar Packages

Security

Security review needed
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
0.2.3 | 01/2012
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.9 | 06/2011
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Unknown
Alert

Unable to detect license

We couldn’t find an appropriate license for this project. It is highly advised to make sure the project license is compatible with your business needs before including it as a dependency, to keep yourself protected from infringement suits or loss of your own code.

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

Limited

Weekly Downloads (321)

Download trend
GitHub Stars
389
Forks
33
Contributors
-

Direct Usage Popularity

The npm package control receives a total of 321 downloads a week. As such, we scored control popularity level to be Limited.

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

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

Community

Limited
Readme.md
No
Contributing.md
No
Code of Conduct
No
Contributors
0
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like control is missing a Code of Conduct.

How about a good first contribution to this project? It seems that control is missing a LICENSE file.

How about a good first contribution to this project? It seems that control is missing a README file.

Embed Package Health Score Badge

package health: 39/100 package health 39/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
0
Open PR
0
Last Release
14 years ago
Last Commit
5 months ago

Further analysis of the maintenance status of control 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 control 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
>=0.6.0
Age
15 years
Dependencies
0 Direct
Versions
19
Install Size
0 B
Dist-tags
3
# of Files
0
Maintainers
1
TS Typings
No

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