tank

v2.0.0

mustang cli For more information about how to use this package see README

Latest version published 3 years ago
License: MIT

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

48 / 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
2.0.0 | 09/2019
Popular
  • 0
    H
  • 0
    M
  • 0
    L
0.0.2 | 08/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

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 (4)

Download trend
Dependents
0
GitHub Stars
0
Forks
0
Contributors
470

Direct Usage Popularity


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

Based on project statistics from the GitHub repository for the npm package tank, we found that it has been starred ? 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.

Community

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

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


Embed Package Health Score Badge

package health: 48/100 package health 48/100

Maintenance

Inactive

Commit Frequency

Open Issues
0
Open PR
0
Last Release
3 years ago
Last Commit
2 years ago

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

Package

Node.js Compatibility
not defined

Age
3 years
Dependencies
13 Direct
Versions
8
Install Size
6.01 kB
Dist-tags
1
# of Files
9
Maintainers
1
TS Typings
No

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