-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bugsnag now contains references to out of date and insecure dependencies -- is an update planned? #170
Comments
Thanks for raising this. We are still maintaining We also wanted to briefly explain why we haven't prioritised work on |
I appreciate that the feature set is evolving, but I do question the decision to de-emphasise security fixes as a result. This makes me (and presumably others) particularly hesitant to recommend/incorporate Bugsnag in my client projects, now and in future, and I am a bit disappointed given that I have only recently made the recommendation that my clients adopt Bugsnag. I see @pmachapman's MR (which is much appreciated), is there anything preventing that from rolling out sooner? |
Cannot add Bugsnag to our projects like this. Please resolve. |
Such minor security issues should be resolved as the highest priority. It is a low-hanging fruit. |
Thank you for your patience and involvement. We consider security issues very seriously, which is why we’ve already scheduled work on the .NET BugSnag library update for the upcoming weeks. We will make the update available as soon as possible and keep you posted on the release. |
Latest version of BugSnag nuget is now very out of date last version is 2022? Is this under active development and support, or is Bugsnag ignoring the .NET ecosystem?
See attached image:
The text was updated successfully, but these errors were encountered: