Vulnerability Database · RubyGems · Package report
rspec_junit_formatter: vulnerability history, versions and safety
rspec_junit_formatter is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the RubyGems ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on rspec_junit_formatter 0.8.0 i
Updated on 23 Oct 2026
Good news: 0.8.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Niche
- Community Quiet
What to do: Stay on 0.8.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.8.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 0.8.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 317 i
- OpenSSF scorecard 2/10 i
- Last release this month i
- Licence MIT i
Version list, release dates, licence and dependants published by RubyGems, 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 rspec_junit_formatter, 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.
- 0.8.0 21 Oct 2026
- 0.7.1 21 Oct 2026
- 0.7.0 21 Oct 2026
- 0.6.2 21 Oct 2026
- 0.6.1 20 Oct 2026
- 0.6.0 29 Sep 2022
- 0.5.1 06 Jan 2022
- 0.5.0 04 Jan 2022
- 0.4.1 30 May 2018
- 0.4.0 26 May 2018
- 0.4.0.pre2 17 Dec 2017
- 0.4.0.pre 05 Dec 2017
- 0.3.0 05 Jul 2017
- 0.3.0.pre6 23 Jun 2017
- 0.3.0.pre5 14 Jun 2017
- 0.3.0.pre4 14 Jun 2017
- 0.3.0.pre3 08 Jun 2017
- 0.3.0.pre2 08 Jun 2017
- 0.3.0.pre 08 Jun 2017
- 0.2.3 03 Jun 2015
- 0.2.2 06 May 2015
- 0.2.1 30 Apr 2015
- 0.2.0 04 Jun 2014
- 0.1.6 04 Feb 2013
- 0.1.5 27 Dec 2012
- 0.1.4 06 Dec 2012
- 0.1.3 20 Nov 2012
- 0.1.2 03 Oct 2012
- 0.1.1 19 Oct 2011
- 0.1.0 24 May 2011
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 0.8.0 | 21 Oct 2026 | none | MIT | — | Details → |
| 0.7.1 | 21 Oct 2026 | none | MIT | — | Details → |
| 0.7.0 | 21 Oct 2026 | none | MIT | — | Details → |
| 0.6.2 | 21 Oct 2026 | none | MIT | — | Details → |
| 0.6.1 | 20 Oct 2026 | none | MIT | — | Details → |
| 0.6.0 | 29 Sep 2022 | none | MIT | — | Details → |
| 0.5.1 | 06 Jan 2022 | none | MIT | — | Details → |
| 0.5.0 | 04 Jan 2022 | none | MIT | — | Details → |
| 0.4.1 | 30 May 2018 | none | MIT | — | Details → |
| 0.4.0 | 26 May 2018 | none | MIT | — | Details → |
| 0.4.0.pre2 | 17 Dec 2017 | none | MIT | — | Details → |
| 0.4.0.pre | 05 Dec 2017 | none | MIT | — | Details → |
| 0.3.0 | 05 Jul 2017 | none | MIT | — | Details → |
| 0.3.0.pre6 | 23 Jun 2017 | none | MIT | — | Details → |
| 0.3.0.pre5 | 14 Jun 2017 | none | MIT | — | Details → |
| 0.3.0.pre4 | 14 Jun 2017 | none | MIT | — | Details → |
| 0.3.0.pre3 | 08 Jun 2017 | none | MIT | — | Details → |
| 0.3.0.pre2 | 08 Jun 2017 | none | MIT | — | Details → |
| 0.3.0.pre | 08 Jun 2017 | none | MIT | — | Details → |
| 0.2.3 | 03 Jun 2015 | none | MIT | — | Details → |
| 0.2.2 | 06 May 2015 | none | MIT | — | Details → |
| 0.2.1 | 30 Apr 2015 | none | MIT | — | Details → |
| 0.2.0 | 04 Jun 2014 | none | MIT | — | Details → |
| 0.1.6 | 04 Feb 2013 | none | — | — | Details → |
| 0.1.5 | 27 Dec 2012 | none | — | — | Details → |
| 0.1.4 | 06 Dec 2012 | none | — | — | Details → |
| 0.1.3 | 20 Nov 2012 | none | — | — | Details → |
| 0.1.2 | 03 Oct 2012 | none | — | — | Details → |
| 0.1.1 | 19 Oct 2011 | none | — | — | Details → |
| 0.1.0 | 24 May 2011 | none | — | — | Details → |
All 30 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 rspec_junit_formatter
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 rspec_junit_formatter
Is rspec_junit_formatter safe to use?
Vulert has no vulnerabilities on record for rspec_junit_formatter in RubyGems 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 rspec_junit_formatter's Vulert package health score?
Vulert scores rspec_junit_formatter 73/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 rspec_junit_formatter affected?
No. 0.8.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.
How many vulnerabilities does rspec_junit_formatter have?
0 vulnerabilities are recorded for rspec_junit_formatter in the RubyGems 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 rspec_junit_formatter vulnerabilities disclosed?
0 vulnerabilities were recorded for rspec_junit_formatter 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 rspec_junit_formatter 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 rspec_junit_formatter for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the rspec_junit_formatter version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.