1. Advisor
  2. JavaScript packages
  3. branch-status

branch-status

v2.0.27

Tool for overviewing issue status in git repo and YouTrack For more information about how to use this package see README

Latest version published 10 months ago
License: Apache-2.0
NPM
GitHub

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

44 / 100

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
2.0.27 | 07/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.26 | 03/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.4.2 | 02/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.0 | 02/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.2.0 | 01/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
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 (11)

Download trend
GitHub Stars
0
Forks
0
Contributors
1

Direct Usage Popularity

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

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

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

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
1
Funding
No

This project has seen only 10 or less contributors.

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

Embed Package Health Score Badge

package health: 44/100 package health 44/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
3
Last Release
10 months ago
Last Commit
4 years ago

Further analysis of the maintenance status of branch-status based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

We found that branch-status demonstrates a positive version release cadence with at least one new version released in the past 12 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
>=10
Age
4 years
Dependencies
9 Direct
Versions
37
Install Size
24.5 kB
Dist-tags
1
# of Files
17
Maintainers
1
TS Typings
No

branch-status 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.