git-stats

v3.2.0

Local git statistics including GitHub-like contributions calendars. For more information about how to use this package see README

Latest version published 1 year 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

62 / 100

Explore Similar Packages

Security

No known security issues
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
3.2.0 | 10/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.1.2 | 10/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.11.0 | 05/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.6.0 | 07/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.5.0 | 05/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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

Small

Weekly Downloads (93)

Download trend
GitHub Stars
6.41K
Forks
183
Contributors
30

Direct Usage Popularity

Occasionally

The npm package git-stats receives a total of 93 downloads a week. As such, we scored git-stats popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package git-stats, we found that it has been starred 6,410 times.

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

Community

Sustainable
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
30
Funding
Yes

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


Embed Package Health Score Badge

package health: 62/100 package health 62/100

Maintenance

Inactive

Commit Frequency

Open Issues
10
Open PR
0
Last Release
1 year ago
Last Commit
3 months ago

Further analysis of the maintenance status of git-stats 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 git-stats 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
10 years
Dependencies
15 Direct
Versions
56
Install Size
54.8 kB
Dist-tags
1
# of Files
7
Maintainers
1
TS Typings
No

git-stats 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.