bugsnag-expo-fork

v5.0.0-alpha.1

Bugsnag error reporter for Expo (fork from official bugsnag repository) For more information about how to use this package see README

Latest version published 6 years ago
License: MIT

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

61 / 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
5.0.0-alpha.1 | 12/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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 (0)

Download trend
GitHub Stars
856
Forks
251
Contributors
50

Direct Usage Popularity


The npm package bugsnag-expo-fork receives a total of 0 downloads a week. As such, we scored bugsnag-expo-fork popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package bugsnag-expo-fork, we found that it has been starred 856 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
No
Contributing.md
Yes
Code of Conduct
No
Contributors
50
Funding
No

With more than 10 contributors for the bugsnag-expo-fork repository, this is possibly a sign for a growing and inviting community.

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

How about a good first contribution to this project? It seems that bugsnag-expo-fork is missing a README file.


Embed Package Health Score Badge

package health: 61/100 package health 61/100

Maintenance

Inactive

Commit Frequency

Open Issues
58
Open PR
21
Last Release
6 years ago
Last Commit
1 month ago

Further analysis of the maintenance status of bugsnag-expo-fork 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 bugsnag-expo-fork 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
not defined

Age
6 years
Dependencies
0 Direct
Versions
2
Install Size
159 kB
Dist-tags
1
# of Files
5
Maintainers
1
TS Typings
No

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