current-git-branch

v1.1.0

A tool to check if files are added in a git repository

MIT
Latest version published about 2 years ago
    npm install current-git-branch
  
We couldn't find any similar packages Browse all packages

Package Health Score

50 / 100
  • Popularity
    Recognized
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Limited

Popularity

Recognized
Weekly Downloads (28,210)
Dependents
147
GitHub Stars
5
Forks
0
Contributors
2

The npm package current-git-branch receives a total of 28,210 downloads a week. As such, we scored current-git-branch popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package current-git-branch, we found that it has been starred 5 times, and that 147 other projects on 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

No known security issues

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

1.0.1
1.1.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.0.1
1.1.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

1.0.1
1.1.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security Policy
No

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

We found a way for you to contribute to the project! Looks like current-git-branch is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test current-git-branch
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
0
Merged PR
2
Open PR
0
Last Commit
2 years ago

Further analysis of the maintenance status of current-git-branch 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 current-git-branch 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
2
Funding
No
License
MIT

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like current-git-branch is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 50/100 package health 50/100

Package

Node.js Compatibility
not defined

Age
4 years
Dependencies
3 Direct / 19 Total
Versions
2
Install Size
206 kB
Dist-tags
1
# of Files
55
Maintainers
1
TS Typings
Yes

We detected a total of 19 direct & transitive dependencies for current-git-branch. See the full dependency tree of current-git-branch

current-git-branch 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.