delete-merged-branch

v1.4.1

A GitHub app built that automatically deletes a branch after it's merged. That's it, enjoy! For more information about how to use this package see README

Latest version published 5 years ago
License: ISC

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
1.4.1 | 09/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.8 | 08/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
ISC
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

Limited

Weekly Downloads (12)

Download trend
GitHub Stars
318
Forks
57
Contributors
10

Direct Usage Popularity

Uncommon

The npm package delete-merged-branch receives a total of 12 downloads a week. As such, we scored delete-merged-branch popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package delete-merged-branch, we found that it has been starred 318 times.

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
10
Funding
No

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 48/100 package health 48/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
7
Open PR
20
Last Release
5 years ago
Last Commit
1 year ago

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

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.

Package

Node.js Compatibility
>= 10.13.0

Age
5 years
Dependencies
1 Direct
Versions
10
Install Size
52.8 kB
Dist-tags
1
# of Files
15
Maintainers
1
TS Typings
No

delete-merged-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.