VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

memory_profiler: vulnerability history, versions and safety

memory_profiler 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.

See all memory_profiler vulnerabilities

Vulert verdict on memory_profiler 1.1.0 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 1.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 25 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 memory_profiler, 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
1.1.0 17 Sep 2024 none MIT — Details →
1.0.2 17 Jun 2024 none MIT — Details →
1.0.1 26 Oct 2022 none MIT — Details →
1.0.0 01 Dec 2020 none MIT — Details →
0.9.14 27 Jun 2019 none MIT — Details →
0.9.13 22 Mar 2019 none MIT — Details →
0.9.12 04 Oct 2018 none MIT — Details →
0.9.11 22 Jul 2018 none MIT — Details →
0.9.10 15 Feb 2018 none MIT — Details →
0.9.9 14 Feb 2018 none MIT — Details →
0.9.8 27 Feb 2017 none MIT — Details →
0.9.7 06 Nov 2016 none MIT — Details →
0.9.6 13 Oct 2015 none MIT — Details →
0.9.5 12 Oct 2015 none MIT — Details →
0.9.4 05 Jun 2015 none MIT — Details →
0.9.3 04 Jun 2015 none MIT — Details →
0.9.2 31 May 2015 none MIT — Details →
0.9.1 25 May 2015 none MIT — Details →
0.9.0 06 Mar 2015 none MIT — Details →
0.0.4 21 Jan 2014 none MIT — Details →
0.0.3 19 Sep 2013 none MIT — Details →
0.0.2 10 Sep 2013 none MIT — Details →
0.0.1 09 Sep 2013 none MIT — Details →

All 23 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 memory_profiler

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 memory_profiler

Is memory_profiler safe to use?

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

Vulert scores memory_profiler 77/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 memory_profiler affected?

No. 1.1.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 memory_profiler should I use?

1.1.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 memory_profiler have?

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

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

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