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

expo-branch

v6.4.0

A unimodule wrapping react-native-branch, enabling its use in Expo managed workflow For more information about how to use this package see README

Latest version published 1 year ago
License: MIT
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

68 / 100

Security

No known security issues
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
6.4.0 | 09/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.3.0 | 08/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.3.0 | 07/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.2.1 | 06/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.1.0 | 03/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

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

Small

Weekly Downloads (10)

Download trend
GitHub Stars
32.5K
Forks
5.15K
Contributors
410

Direct Usage Popularity

TOP 30%

The npm package expo-branch receives a total of 10 downloads a week. As such, we scored expo-branch popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package expo-branch, we found that it has been starred 32,502 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
No
Contributors
410
Funding
No

A good and healthy external contribution signal for expo-branch project, which invites more than one hundred open source maintainers to collaborate on the repository.

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

Embed Package Health Score Badge

package health: 68/100 package health 68/100

Maintenance

Inactive

Commit Frequency

Open Issues
420
Open PR
247
Last Release
1 year ago
Last Commit
2 months ago

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

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
not defined
Age
5 years
Dependencies
1 Direct
Versions
32
Install Size
149 kB
Dist-tags
2
# of Files
57
Maintainers
29
TS Typings
No

expo-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.