git-hours

v1.3.0

Estimate time spent on a git repository

MIT
Latest version published 5 years ago
    npm install git-hours
  

Explore Similar Packages

Package Health Score

48 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Limited

Weekly Downloads (31)

Download trend
Dependents
0
GitHub Stars
516
Forks
50
Contributors
20

Direct Usage Popularity


The npm package git-hours receives a total of 31 downloads a week. As such, we scored git-hours popularity level to be Limited.

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

07/2014
07/2014
03/2016
06/2016

Direct Vulnerabilities

0.1.9
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.2.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.2.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.3.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular

License Risk

0.1.9
  • 0
    H
  • 0
    M
  • 0
    L
0.2.0
  • 0
    H
  • 0
    M
  • 0
    L
1.2.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
1.3.0
  • 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 git-hours 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 git-hours
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
16
Open PR
7
Last Release
5 years ago
Last Commit
7 months ago

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

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

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

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


Embed Package Health Score Badge

package health: 48/100 package health 48/100

Package

Node.js Compatibility
not defined

Age
7 years
Dependencies
5 Direct
Versions
11
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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