Vulnerability Database · RubyGems · Package report

rspec-mocks: vulnerability history, versions and safety

rspec-mocks is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems 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.

Vulert verdict on rspec-mocks 3.13.8 i

Updated on 23 Oct 2026

Good news: 3.13.8, the version you would install today, has no known vulnerabilities.

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 3.13.8 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,866 i
  • OpenSSF scorecard 4/10 i
  • Last release 7 months ago 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-mocks, 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
3.13.8 27 Feb 2026 none MIT — Details →
4.0.0.beta1 18 Feb 2026 none MIT — Details →
3.13.7 31 Oct 2025 none MIT — Details →
3.13.6 14 Oct 2025 none MIT — Details →
3.13.5 27 May 2025 none MIT — Details →
3.13.4 05 May 2025 none MIT — Details →
3.13.3 01 May 2025 none MIT — Details →
3.13.2 02 Oct 2024 none MIT — Details →
3.13.1 08 May 2024 none MIT — Details →
3.13.0 04 Feb 2024 none MIT — Details →
3.12.7 04 Feb 2024 none MIT — Details →
3.12.6 11 Jul 2023 none MIT — Details →
3.12.5 30 Mar 2023 none MIT — Details →
3.12.4 12 Mar 2023 none MIT — Details →
3.12.3 17 Jan 2023 none MIT — Details →
3.12.2 07 Jan 2023 none MIT — Details →
3.12.1 10 Dec 2022 none MIT — Details →
3.12.0 26 Oct 2022 none MIT — Details →
3.11.2 25 Oct 2022 none MIT — Details →
3.11.1 31 Mar 2022 none MIT — Details →
3.11.0 09 Feb 2022 none MIT — Details →
3.10.3 28 Jan 2022 none MIT — Details →
3.10.2 28 Jan 2021 none MIT — Details →
3.10.1 28 Dec 2020 none MIT — Details →
3.10.0 30 Oct 2020 none MIT — Details →
3.9.1 31 Dec 2019 none MIT — Details →
3.9.0 07 Oct 2019 none MIT — Details →
3.8.2 02 Oct 2019 none MIT — Details →
3.8.1 13 Jun 2019 none MIT — Details →
3.8.0 04 Aug 2018 none MIT — Details →
3.7.0 17 Oct 2017 none MIT — Details →
3.6.0 04 May 2017 none MIT — Details →
3.6.0.beta2 12 Dec 2016 none MIT — Details →
3.6.0.beta1 10 Oct 2016 none MIT — Details →
3.5.0 01 Jul 2016 none MIT — Details →
3.5.0.beta4 05 Jun 2016 none MIT — Details →
3.5.0.beta3 02 Apr 2016 none MIT — Details →
3.5.0.beta2 10 Mar 2016 none MIT — Details →
3.5.0.beta1 06 Feb 2016 none MIT — Details →
3.4.1 10 Jan 2016 none MIT — Details →
3.4.0 12 Nov 2015 none MIT — Details →
3.3.2 15 Jul 2015 none MIT — Details →
3.3.1 20 Jun 2015 none MIT — Details →
2.99.4 20 Jun 2015 none MIT — Details →
3.3.0 12 Jun 2015 none MIT — Details →
3.2.1 24 Feb 2015 none MIT — Details →
3.2.0 03 Feb 2015 none MIT — Details →
2.99.3 10 Jan 2015 none MIT — Details →
3.1.3 09 Oct 2014 none MIT — Details →
3.1.2 26 Sep 2014 none MIT — Details →
3.1.1 18 Sep 2014 none MIT — Details →
3.1.0 05 Sep 2014 none MIT — Details →
3.0.4 14 Aug 2014 none MIT — Details →
3.0.3 21 Jul 2014 none MIT — Details →
2.99.2 21 Jul 2014 none MIT — Details →
3.0.2 20 Jun 2014 none MIT — Details →
2.99.1 12 Jun 2014 none MIT — Details →
3.0.1 07 Jun 2014 none MIT — Details →
3.0.0 02 Jun 2014 none MIT — Details →
2.99.0 01 Jun 2014 none MIT — Details →
3.0.0.rc1 18 May 2014 none MIT — Details →
2.99.0.rc1 18 May 2014 none MIT — Details →
2.14.6 20 Feb 2014 none MIT — Details →
3.0.0.beta2 18 Feb 2014 none MIT — Details →
2.99.0.beta2 18 Feb 2014 none MIT — Details →
2.14.5 01 Feb 2014 none MIT — Details →
3.0.0.beta1 08 Nov 2013 none MIT — Details →
2.99.0.beta1 07 Nov 2013 none MIT — Details →
2.14.4 16 Oct 2013 none MIT — Details →
2.14.3 09 Aug 2013 none MIT — Details →
2.14.2 30 Jul 2013 none MIT — Details →
2.14.1 08 Jul 2013 none MIT — Details →
2.14.0 06 Jul 2013 none MIT — Details →
2.14.0.rc1 27 May 2013 none MIT — Details →
2.13.1 07 Apr 2013 none MIT — Details →
2.13.0 23 Feb 2013 none MIT — Details →
2.12.2 28 Jan 2013 none MIT — Details →
2.12.1 21 Dec 2012 none MIT — Details →
2.12.0 13 Nov 2012 none — — Details →
2.11.3 20 Sep 2012 none — — Details →
2.11.2 12 Aug 2012 none — — Details →
2.11.1 10 Jul 2012 none — — Details →
2.11.0 07 Jul 2012 none — — Details →
2.10.1 05 May 2012 none — — Details →
2.10.0 04 May 2012 none — — Details →
2.9.0 17 Mar 2012 none — — Details →
2.9.0.rc2 12 Mar 2012 none — — Details →
2.8.0 05 Jan 2012 none — — Details →
2.8.0.rc2 20 Dec 2011 none — — Details →
2.8.0.rc1 06 Nov 2011 none — — Details →
2.7.0 16 Oct 2011 none — — Details →
2.7.0.rc1 09 Oct 2011 none — — Details →
2.6.0 12 May 2011 none — — Details →
2.6.0.rc6 06 May 2011 none — — Details →
2.6.0.rc4 01 May 2011 none — — Details →
2.6.0.rc2 18 Apr 2011 none — — Details →
2.5.0 05 Feb 2011 none — — Details →
2.4.0 02 Jan 2011 none — — Details →
2.3.0 12 Dec 2010 none — — Details →
2.2.0 28 Nov 2010 none — — Details →
2.1.0 07 Nov 2010 none — — Details →
2.0.1 19 Oct 2010 none — — Details →
2.0.0 10 Oct 2010 none — — Details →
2.0.0.rc 05 Oct 2010 none — — Details →
2.0.0.beta.22 13 Sep 2010 none — — Details →
2.0.0.beta.20 24 Aug 2010 none — — Details →
2.0.0.beta.19 26 Jul 2010 none — — Details →
2.0.0.beta.18 22 Jul 2010 none — — Details →
2.0.0.beta.17 11 Jul 2010 none — — Details →
2.0.0.beta.16 07 Jul 2010 none — — Details →
2.0.0.beta.15 30 Jun 2010 none — — Details →
2.0.0.beta.14 28 Jun 2010 none — — Details →
2.0.0.beta.13 24 Jun 2010 none — — Details →
2.0.0.beta.12 14 Jun 2010 none — — Details →
2.0.0.beta.11 07 Jun 2010 none — — Details →
2.0.0.beta.10 03 Jun 2010 none — — Details →
2.0.0.beta.9 27 May 2010 none — — Details →
2.0.0.beta.8 27 Apr 2010 none — — Details →
2.0.0.beta.7 17 Apr 2010 none — — Details →
2.0.0.beta.6 12 Apr 2010 none — — Details →

The newest 120 of 135 versions Vulert tracks. 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-mocks

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 rspec-mocks

Is rspec-mocks safe to use?

Vulert has no vulnerabilities on record for rspec-mocks 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-mocks's Vulert package health score?

Vulert scores rspec-mocks 81/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-mocks affected?

No. 3.13.8, 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 rspec-mocks should I use?

3.13.8 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 rspec-mocks have?

0 vulnerabilities are recorded for rspec-mocks 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-mocks vulnerabilities disclosed?

0 vulnerabilities were recorded for rspec-mocks 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-mocks 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-mocks for upcoming vulnerabilities?

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