Make sure the open source you're using is safe to use
git-branch
v2.0.1Get the current branch from the local git repository.
npm install git-branch
Explore Similar Packages
Package Health Score
47 / 100
- Popularity Recognized
- Maintenance Inactive
- Security No known security issues
- Community Limited
Make sure the open source you're using is safe to usePopularity
Recognized
Weekly Downloads (46,171)- Dependents
- 234
- GitHub Stars
- 80
- Forks
- 11
- Contributors
- 3
The npm package git-branch receives a total of 46,171 downloads a week. As such, we scored git-branch popularity level to be Recognized.
Based on project statistics from the GitHub repository for the npm package git-branch, we found that it has been starred 80 times, and that 234 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
No known security issues
Security and license risk for significant versions
All VersionsDirect Vulnerabilities
0.1.2
0.2.0
0.3.0
1.0.0
2.0.1
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
Indirect Vulnerabilities
0.1.2
0.2.0
0.3.0
1.0.0
2.0.1
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
License Risks
0.1.2
0.2.0
0.3.0
1.0.0
2.0.1
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
- 0H
- 0M
- 0L
All security vulnerabilities belong to
production dependencies of direct and indirect
packages.
We found a way for you to contribute to the project! Looks like git-branch 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.
We found a way for you to contribute to the project! Looks like git-branch is missing a security policy.
# Install the Snyk CLI and test your project
npm i snyk && snyk test git-branch
Maintenance
Inactive
Commit Frequency- Open Issues
- 5
- Merged PR
- 3
- Open PR
- 1
- Last Commit
- 2 years ago
Further analysis of the maintenance status of 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 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
- No
- Contributing.md
- No
- Code of Conduct
- No
- Contributors
- 3
- Funding
- No
This project has seen only 10 or less contributors.
We found a way for you to contribute to the project! Looks like git-branch is missing a Code of Conduct.
How about a good first contribution to this project? It seems that git-branch is missing a README file.
Embed Package Health Score Badge
Package
- Node.js Compatibility
- >=8
- Age
- 7 years
- Dependencies
- 1 Direct / 95 Total
- Versions
- 9
- Install Size
- 6.91 kB
- Dist-tags
- 1
- # of Files
- 4
- Maintainers
- 1
- TS Typings
- Yes
We detected a total of 95 direct & transitive dependencies for git-branch. See the full dependency tree of git-branch
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.
git-branch 
Get the current branch from the local git repository.
Please consider following this project's author, Jon Schlinkert, and consider starring the project to show your ❤️ and support.
Install
Install with npm:
$ npm install --save git-branch
Usage
const branch = require('git-branch');
Optionally pass the cwd (current working directory) as the first argument.
Promise
branch('some/path')
.then(name => console.log('Branch:', name)) //=> 'master'
.catch(console.error);
Callback
branch(function(err, name) {
if (err) throw err;
console.log('Branch:', name); //=> 'master'
});
Sync
console.log('Branch:', branch.sync()); //=> 'master'
About
Contributing
Pull requests and stars are always welcome. For bugs and feature requests, please create an issue.
Running Tests
Running and reviewing unit tests is a great way to get familiarized with a library and its API. You can install dependencies and run tests with the following command:
$ npm install && npm test
Building docs
(This project's readme.md is generated by verb, please don't edit the readme directly. Any changes to the readme must be made in the .verb.md readme template.)
To generate the readme, run the following command:
$ npm install -g verbose/verb#dev verb-generate-readme && verb
Related projects
You might also be interested in these projects:
- git-add-remote: API for adding git remotes. | homepage
- git-user-name: Get a user's name from git config at the project or global scope, depending on… more | homepage
- github-base: JavaScript wrapper that greatly simplifies working with GitHub's API. | homepage
Contributors
| Commits | Contributor |
|---|---|
| 19 | jonschlinkert |
| 6 | emilrowland |
Author
Jon Schlinkert
License
Copyright © 2018, Jon Schlinkert. Released under the MIT License.
This file was generated by verb-generate-readme, v0.6.0, on March 09, 2018.
git-branch versions
| Version | Published | Tag | Node.js Compatability | Licenses | Dependencies | Direct Vulnerabilities | Publisher |
|---|---|---|---|---|---|---|---|
| 2.0.1 | 09 March 2018 | latest | >=8 | MIT | 1 |
| jonschlinkert |
| 1.0.0 | 02 June 2017 | >=0.8 | MIT | 0 |
| jonschlinkert | |
| 0.3.0 | 09 March 2015 | >=0.8 | MIT | 0 |
| jonschlinkert | |
| All Versions | |||||||
git-branch dependencies
Last updated on
17 January-2021, at 11:50 (UTC).