Vulnerability Database · Go · Package report
github.com/bugsnag/panicwrap: vulnerability history, versions and safety
github.com/bugsnag/panicwrap is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/bugsnag/panicwrap v1.3.4 i
Updated on 23 Oct 2026
Good news: v1.3.4, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Quiet
What to do: Stay on v1.3.4 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.3.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.3.4 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 36 i
- OpenSSF scorecard 2/10 i
- Last release 62 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/bugsnag/panicwrap, 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.
- v0.0.0-20210810111631-d61e71752190 10 Aug 2021
- v1.3.4 10 Aug 2021
- v1.3.4-0.20210810111631-d61e71752190 10 Aug 2021
- v1.3.3 13 Jul 2021
- v1.3.3-0.20210530212736-826a46b67680 30 May 2021
- v1.3.2 25 Mar 2021
- v1.3.1 12 Jan 2021
- v1.3.1-0.20210111104856-3f8ccef16108 11 Jan 2021
- v1.3.0 05 Jan 2021
- v1.2.3-0.20210104143206-665b91ce4b4d 04 Jan 2021
- v1.2.3-0.20201221161223-96c8a1da895f 21 Dec 2020
- v1.2.2 17 Dec 2020
- v1.2.1 04 Dec 2020
- v1.2.1-0.20201105163724-2f452343ad53 05 Nov 2020
- v0.0.0-20180510051541-1d162ee1264c 10 May 2018
- v1.2.1-0.20180510051541-1d162ee1264c 10 May 2018
- v0.0.0-20170829152406-dd8df9a3778a 29 Aug 2017
- v1.2.1-0.20170829152406-dd8df9a3778a 29 Aug 2017
- v0.0.0-20170808195354-4009b2b7c78d 08 Aug 2017
- v1.2.0 08 Aug 2017
- v0.0.0-20170621001252-5ee3ef22a494 21 Jun 2017
- v0.0.0-20170615235621-8a46439dfbe6 15 Jun 2017
- v0.0.0-20160912155506-aa7703c9414b 12 Sep 2016
- v0.0.0-20160905164545-ef559154a4fe 05 Sep 2016
- v0.0.0-20160905164439-15d85cffc73b 05 Sep 2016
- v0.0.0-20160401221449-d6191e27ad06 01 Apr 2016
- v0.0.0-20160118154447-aceac81c6e2f 18 Jan 2016
- v0.0.0-20151223152923-e2c28503fcd0 23 Dec 2015
- v0.0.0-20151223120756-ad92ce47d64d 23 Dec 2015
- v0.0.0-20141110184334-e5f9854865b9 10 Nov 2014
- v0.0.0-20141110183811-dcc0b1f08206 10 Nov 2014
- v0.0.0-20141008052627-dbbd17736f5e 08 Oct 2014
- v0.0.0-20141008052055-944c4663e1de 08 Oct 2014
- v0.0.0-20140817062020-f3364afc9e78 17 Aug 2014
- v0.0.0-20140530154129-0cfb3de48c53 30 May 2014
- v0.0.0-20130813212737-2c0d91a9eb46 13 Aug 2013
All 36 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/bugsnag/panicwrap
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
Questions
About github.com/bugsnag/panicwrap
Is github.com/bugsnag/panicwrap safe to use?
Vulert has no vulnerabilities on record for github.com/bugsnag/panicwrap 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/bugsnag/panicwrap's Vulert package health score?
Vulert scores github.com/bugsnag/panicwrap 45/100, which reads as risky. 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/bugsnag/panicwrap affected?
No. v1.3.4, 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/bugsnag/panicwrap should I use?
v1.3.4 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/bugsnag/panicwrap have?
0 vulnerabilities are recorded for github.com/bugsnag/panicwrap 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/bugsnag/panicwrap vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/bugsnag/panicwrap 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/bugsnag/panicwrap 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/bugsnag/panicwrap for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/bugsnag/panicwrap version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.