@bugsnag/expo

v52.0.0

Bugsnag error reporter for Expo applications For more information about how to use this package see README

Latest version published 25 days 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

71 / 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
52.0.0 | 11/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
51.0.1 | 08/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
51.0.0 | 05/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
50.0.0 | 02/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
49.0.2 | 12/2023
  • 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

Recognized

Weekly Downloads (10,005)

Download trend
GitHub Stars
10
Forks
5
Contributors
30

Direct Usage Popularity

TOP 30%

The npm package @bugsnag/expo receives a total of 10,005 downloads a week. As such, we scored @bugsnag/expo popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package @bugsnag/expo, we found that it has been starred 10 times.

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

Community

Sustainable
Readme.md
No
Contributing.md
Yes
Code of Conduct
No
Contributors
30
Funding
No

With more than 10 contributors for the @bugsnag/expo 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 is missing a Code of Conduct.

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


Embed Package Health Score Badge

package health: 71/100 package health 71/100

Maintenance

Healthy

Commit Frequency

Open Issues
8
Open PR
4
Last Release
25 days ago
Last Commit
5 months ago

Further analysis of the maintenance status of @bugsnag/expo based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Healthy.

We found that @bugsnag/expo demonstrates a positive version release cadence with at least one new version released in the past 3 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.

Package

Node.js Compatibility
not defined

Age
6 years
Dependencies
15 Direct
Versions
105
Install Size
12.1 kB
Dist-tags
4
# of Files
9
Maintainers
9
TS Typings
Yes

@bugsnag/expo 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.