1. Advisor
  2. JavaScript packages
  3. bugsnag-js

bugsnag-js

v4.7.3

Automatically detect JavaScript errors, collect detailed diagnostic information, and get notified about errors in real-time. For more information about how to use this package see README

Latest version published 6 years 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

56 / 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
4.7.3 | 08/2018
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.6.3 | 05/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.3.3 | 12/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.5.0 | 02/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.4.9 | 12/2015
  • 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

Small

Weekly Downloads (3,095)

Download trend
GitHub Stars
855
Forks
252
Contributors
50

Direct Usage Popularity

TOP 5%

The npm package bugsnag-js receives a total of 3,095 downloads a week. As such, we scored bugsnag-js popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package bugsnag-js, we found that it has been starred 855 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
50
Funding
No

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

Embed Package Health Score Badge

package health: 56/100 package health 56/100

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
58
Open PR
18
Last Release
6 years ago
Last Commit
11 days ago

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

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
10 years
Dependencies
6 Direct
Versions
71
Install Size
1.02 MB
Dist-tags
2
# of Files
90
Maintainers
3
TS Typings
Yes

bugsnag-js 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.