Vulnerability Database · Go · Package report
github.com/jstemmer/go-junit-report: vulnerability history, versions and safety
github.com/jstemmer/go-junit-report 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/jstemmer/go-junit-report v1.0.0 i
Updated on 23 Oct 2026
Good news: v1.0.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.0.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 824 i
- OpenSSF scorecard 4/10 i
- Last release 55 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/jstemmer/go-junit-report, 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.0.1-0.20220306230355-2a37e36ac673 06 Mar 2022
- v1.0.1-0.20220226233952-d5de2960fd17 26 Feb 2022
- v1.0.1-0.20220226233129-e0c48d5051f1 26 Feb 2022
- v1.0.0 24 Feb 2022
- v0.9.2-0.20220224220047-b61b86b9a775 24 Feb 2022
- v0.9.2-0.20191008223341-afccc651b777 08 Oct 2019
- v0.0.0-20191008195320-984a47ca6b0a 08 Oct 2019
- v0.9.2-0.20191008195320-984a47ca6b0a 08 Oct 2019
- v0.0.0-20191004195537-cc1f095d5cc5 04 Oct 2019
- v0.9.1 04 Oct 2019
- v0.9.0 03 Oct 2019
- v0.0.0-20191003230501-27e2e8f78299 03 Oct 2019
- v0.0.0-20191003215814-8b849e7995d2 03 Oct 2019
- v0.0.0-20191003211110-080dff894f9e 03 Oct 2019
- v0.0.0-20190919004454-6315b3013bf1 19 Sep 2019
- v0.0.0-20190106144839-af01ea7f8024 06 Jan 2019
- v0.0.0-20180614143834-385fac0ced9a 14 Jun 2018
- v0.0.0-20180608195633-d0a98937db51 08 Jun 2018
- v0.0.0-20180603214925-47abdc7385e3 03 Jun 2018
- v0.0.0-20180603192848-1c2c0a00fec0 03 Jun 2018
- v0.0.0-20180421171502-1ce4b93a20c6 21 Apr 2018
- v0.0.0-20180317202424-f738270caf65 17 Mar 2018
- v0.0.0-20180203235050-d9db44172dfb 03 Feb 2018
- v0.0.0-20170728204303-a009038a6334 28 Jul 2017
- v0.0.0-20170724204557-15422cf504f9 24 Jul 2017
- v0.0.0-20170511212243-cce73b49960a 11 May 2017
- v0.0.0-20170401113820-e02a3f88c092 01 Apr 2017
- v0.0.0-20170326225837-c60683206576 26 Mar 2017
- v0.0.0-20170122081301-3c05bc8cb6a5 22 Jan 2017
- v0.0.0-20161110005800-6aeed679b62e 10 Nov 2016
- v0.0.0-20150903121937-833f8ea2b99d 03 Sep 2015
- v0.0.0-20150701203212-8faee8c123c7 01 Jul 2015
All 32 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/jstemmer/go-junit-report
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/jstemmer/go-junit-report
Is github.com/jstemmer/go-junit-report safe to use?
Vulert has no vulnerabilities on record for github.com/jstemmer/go-junit-report 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/jstemmer/go-junit-report's Vulert package health score?
Vulert scores github.com/jstemmer/go-junit-report 60/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/jstemmer/go-junit-report affected?
No. v1.0.0, 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/jstemmer/go-junit-report should I use?
v1.0.0 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/jstemmer/go-junit-report have?
0 vulnerabilities are recorded for github.com/jstemmer/go-junit-report 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/jstemmer/go-junit-report vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/jstemmer/go-junit-report 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/jstemmer/go-junit-report 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/jstemmer/go-junit-report for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jstemmer/go-junit-report version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.