VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/Shopify/logrus-bugsnag: vulnerability history, versions and safety

github.com/Shopify/logrus-bugsnag is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/Shopify/logrus-bugsnag vulnerabilities

Vulert verdict on github.com/Shopify/logrus-bugsnag v0.0.0-20250605201603-d55aa3c8353b i

Updated on 23 Oct 2026

Good news: v0.0.0-20250605201603-d55aa3c8353b, the version you would install today, has no known vulnerabilities.

Package health score 65/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on v0.0.0-20250605201603-d55aa3c8353b or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20250605201603-d55aa3c8353b too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.0.0-20250605201603-d55aa3c8353b — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 13 i
  • Last release 16 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/Shopify/logrus-bugsnag, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20250723164530-d710743bf0b2 23 Jul 2025 none MIT — Details →
v0.0.0-20250723160110-f74ce316da99 23 Jul 2025 none MIT — Details →
v0.0.0-20250605201603-d55aa3c8353b 05 Jun 2025 none MIT — Details →
v0.0.0-20250429205613-5f639c36f9be 29 Apr 2025 none MIT — Details →
v0.0.0-20240726201947-15ec56b7745a 26 Jul 2024 none MIT — Details →
v0.0.0-20240617022239-c1ef25b464fd 17 Jun 2024 none MIT — Details →
v0.0.0-20240520024219-5c98f4680d62 20 May 2024 none MIT — Details →
v0.0.0-20240513025901-03aac5d9a704 13 May 2024 none MIT — Details →
v0.0.0-20240507214313-004243a594f4 07 May 2024 none MIT — Details →
v0.0.0-20240506025140-f35b5b1c8b78 06 May 2024 none MIT — Details →
v0.0.0-20240429024657-5523bdf94c12 29 Apr 2024 none MIT — Details →
v0.0.0-20240422022907-2489c30f59c7 22 Apr 2024 none MIT — Details →
v0.0.0-20240416025716-b23c7bc2904c 16 Apr 2024 none MIT — Details →
v0.0.0-20240408024128-40183b9ae1eb 08 Apr 2024 none MIT — Details →
v0.0.0-20240403025918-366509574f7d 03 Apr 2024 none MIT — Details →
v0.0.0-20230814024721-81546a0197a8 14 Aug 2023 none MIT — Details →
v0.0.0-20230619030253-b6ad45ecdec1 19 Jun 2023 none MIT — Details →
v0.0.0-20230327050321-8cb14ae75c26 27 Mar 2023 none MIT — Details →
v0.0.0-20230117174420-439a4b8ba167 17 Jan 2023 none MIT — Details →
v0.0.0-20230117170210-cb91f57f64e0 17 Jan 2023 none MIT — Details →
v0.0.0-20230117170055-0ad6b5c31307 17 Jan 2023 none MIT — Details →
v0.0.0-20171204204709-577dee27f20d 04 Dec 2017 none MIT — Details →
v0.0.0-20170309145241-6dbc35f2c30d 09 Mar 2017 none MIT — Details →
v0.0.0-20170309144909-92ba86c20751 09 Mar 2017 none MIT — Details →
v0.0.0-20160811013905-797fa877e4ab 11 Aug 2016 none MIT — Details →
v0.0.0-20160517173102-5a46080c635f 17 May 2016 none MIT — Details →
v0.0.0-20151022192904-63e11ff9385c 22 Oct 2015 none — — Details →

All 27 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for github.com/Shopify/logrus-bugsnag

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/Shopify/logrus-bugsnag

Is github.com/Shopify/logrus-bugsnag safe to use?

Vulert has no vulnerabilities on record for github.com/Shopify/logrus-bugsnag in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is github.com/Shopify/logrus-bugsnag's Vulert package health score?

Vulert scores github.com/Shopify/logrus-bugsnag 65/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/Shopify/logrus-bugsnag affected?

No. v0.0.0-20250605201603-d55aa3c8353b, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of github.com/Shopify/logrus-bugsnag should I use?

v0.0.0-20250605201603-d55aa3c8353b is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/Shopify/logrus-bugsnag have?

0 vulnerabilities are recorded for github.com/Shopify/logrus-bugsnag in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/Shopify/logrus-bugsnag vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/Shopify/logrus-bugsnag in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/Shopify/logrus-bugsnag are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/Shopify/logrus-bugsnag for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/Shopify/logrus-bugsnag version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.