VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

high_voltage: vulnerability history, versions and safety

high_voltage 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 high_voltage vulnerabilities

Vulert verdict on high_voltage 5.0.0 i

Updated on 23 Oct 2026

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

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

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

  • Current release 5.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 11 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 high_voltage, 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
5.0.0 24 Oct 2025 none MIT — Details →
4.0.0 31 May 2024 none MIT — Details →
4.0.0.rc1 25 Mar 2024 none MIT — Details →
3.1.2 20 May 2019 none MIT — Details →
3.1.1 14 May 2019 none MIT — Details →
3.1.0 04 May 2018 none MIT — Details →
3.0.0 15 Apr 2016 none MIT — Details →
2.4.0 17 Jul 2015 none MIT — Details →
2.3.0 17 Apr 2015 none MIT — Details →
2.2.1 23 Jul 2014 none MIT — Details →
2.2.0 24 Jun 2014 none MIT — Details →
2.1.0 30 Dec 2013 none MIT — Details →
2.0.0 05 Oct 2013 none MIT — Details →
1.2.4 19 Jul 2013 none — — Details →
1.2.3 15 Jun 2013 none — — Details →
1.2.2 17 Feb 2013 none — — Details →
1.2.1 30 Oct 2012 none — — Details →
1.2.0 27 Aug 2012 none — — Details →
1.1.1 23 Feb 2012 none — — Details →
1.1.0 23 Feb 2012 none — — Details →
1.0.1 04 Sep 2011 none — — Details →
1.0.0 29 Jun 2011 none — — Details →
0.9.4 09 Apr 2011 none — — Details →
0.9.3 30 Dec 2010 none — — Details →
0.9.2 25 Oct 2010 none — — Details →
0.9.1 22 Aug 2010 none — — Details →
0.9.0 20 Apr 2010 none — — Details →

All 27 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 high_voltage

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 high_voltage

Is high_voltage safe to use?

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

Vulert scores high_voltage 94/100, which reads as healthy. 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 high_voltage affected?

No. 5.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 high_voltage should I use?

5.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 high_voltage have?

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

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

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