Vulnerability Database · Go · Package report
github.com/opentracing-contrib/go-stdlib: vulnerability history, versions and safety
github.com/opentracing-contrib/go-stdlib 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.
See all github.com/opentracing-contrib/go-stdlib vulnerabilities
Vulert verdict on github.com/opentracing-contrib/go-stdlib v1.1.1 i
Updated on 23 Oct 2026
Good news: v1.1.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on v1.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 223 i
- OpenSSF scorecard 3/10 i
- Last release 9 months ago i
- Licence Apache-2.0 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/opentracing-contrib/go-stdlib, 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.
- v1.1.2-0.20261006012544-413e7ded0ddf 06 Oct 2026
- v1.1.2-0.20260921204913-e1d1b2b10462 21 Sep 2026
- v1.1.2-0.20260810224153-2b1b81169ad2 10 Aug 2026
- v1.1.2-0.20260721020921-6920a47c507d 21 Jul 2026
- v1.1.2-0.20260721004633-7ffec8fc3f13 21 Jul 2026
- v1.1.2-0.20260624013457-cd1038425cfa 24 Jun 2026
- v1.1.2-0.20260528155411-f102363ff79b 28 May 2026
- v1.1.2-0.20260228010559-ca847c6a6c58 28 Feb 2026
- v1.1.2-0.20260120234311-245ec809547a 20 Jan 2026
- v1.1.1 08 Jan 2026
- v1.1.1-0.20250917170132-a91258e24258 17 Sep 2025
- v1.1.1-0.20250401182519-7754fedb557e 01 Apr 2025
- v1.1.1-0.20250315015301-200b2ae56d25 15 Mar 2025
- v1.1.1-0.20250301210218-4eb3d6f0fcf4 01 Mar 2025
- v0.0.0-20241203015719-09b6f447e1a1 03 Dec 2024
- v1.0.1-0.20241108174859-a42dde86ee60 08 Nov 2024
- v1.1.0 08 Nov 2024
- v1.0.1-0.20241108020803-191ea6aacc62 08 Nov 2024
- v1.0.1-0.20210923165142-fec77c82c616 23 Sep 2021
- v1.0.1-0.20210923164924-a144f182e20c 23 Sep 2021
- v0.0.0-20210423174146-00fa856341a8 23 Apr 2021
- v1.0.1-0.20210423174146-00fa856341a8 23 Apr 2021
- v1.0.1-0.20201217190255-08d136d2c7db 17 Dec 2020
- v1.0.1-0.20201108205343-60eb967dd208 08 Nov 2020
- v1.0.1-0.20201028152118-adbfc141dfc2 28 Oct 2020
- v1.0.1-0.20200721161309-b117d4f647fb 21 Jul 2020
- v0.0.0-20200608040608-8a6ff1ad1691 08 Jun 2020
- v1.0.0 08 Jun 2020
- v0.9.1-0.20200607235844-8d81dee4a93d 07 Jun 2020
- v0.0.0-20190519235532-cf7a6c988dc9 19 May 2019
- v0.9.0 19 May 2019
- v0.0.0-20190510164024-2b2d2700a3b7 10 May 2019
- v0.0.0-20190324214902-3020fec0e66b 24 Mar 2019
- v0.0.0-20190324004232-a7d9dae69ffb 24 Mar 2019
- v0.0.0-20190315153516-431a6bc76b48 15 Mar 2019
- v0.0.0-20190205184154-464eb271c715 05 Feb 2019
- v0.0.0-20181222025249-77df8e8e70b4 22 Dec 2018
- v0.0.0-20181213181119-09659152d0aa 13 Dec 2018
- v0.0.0-20181101210145-c9628a4f0148 01 Nov 2018
- v0.0.0-20180702182724-07a764486eb1 02 Jul 2018
- v0.0.0-20180313041242-367231351874 13 Mar 2018
- v0.0.0-20180308002341-f6b9967a3c69 08 Mar 2018
- v0.0.0-20171029140428-b1a47cfbdd75 29 Oct 2017
- v0.0.0-20171028183014-030850cf3f7f 28 Oct 2017
- v0.0.0-20170528224940-48e4d763b2fb 28 May 2017
- v0.0.0-20170526151951-8e85ebac6ca1 26 May 2017
- v0.0.0-20170428175314-24ef76428deb 28 Apr 2017
- v0.0.0-20170113013457-1de4cc2120e7 13 Jan 2017
- v0.0.0-20161004200401-75e37ae3e209 04 Oct 2016
- v0.0.0-20161004200352-33b4df363942 04 Oct 2016
- v0.0.0-20160925191042-0092e1d6af12 25 Sep 2016
- v0.0.0-20160917091904-3306042dbb02 17 Sep 2016
- v0.0.0-20160720222056-070d4046d1a7 20 Jul 2016
- v0.0.0-20160720222056-dabe12a3518e 20 Jul 2016
- v0.0.0-20160720222052-98e995ad24c8 20 Jul 2016
All 55 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/opentracing-contrib/go-stdlib
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/opentracing-contrib/go-stdlib
Is github.com/opentracing-contrib/go-stdlib safe to use?
Vulert has no vulnerabilities on record for github.com/opentracing-contrib/go-stdlib 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/opentracing-contrib/go-stdlib's Vulert package health score?
Vulert scores github.com/opentracing-contrib/go-stdlib 70/100, which reads as in good shape. 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/opentracing-contrib/go-stdlib affected?
No. v1.1.1, 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/opentracing-contrib/go-stdlib should I use?
v1.1.1 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/opentracing-contrib/go-stdlib have?
0 vulnerabilities are recorded for github.com/opentracing-contrib/go-stdlib 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/opentracing-contrib/go-stdlib vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/opentracing-contrib/go-stdlib 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/opentracing-contrib/go-stdlib 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/opentracing-contrib/go-stdlib for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/opentracing-contrib/go-stdlib version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.