Was ruby-lsp Hacked?

No Publicly Reported Incidents. As of June 2026, ruby-lsp has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev. Nerq's automated security analysis rates ruby-lsp's security posture as strong (security dimension score: 90/100). Trust Score: 68/100 (B-). Last checked: 2026-06-15.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score68/100 (B-)
Security Dimension90/100
PublisherShopify
RegistryN/A

What We Check

Full Trust Analysis

For a complete safety assessment including privacy, maintenance, and community trust signals, see ruby-lsp Trust Score on Nerq.

FAQ

Has ruby-lsp been hacked?
As of June 2026, ruby-lsp has no publicly reported security breaches, hacks, or CVE entries in the databases Nerq monitors. This covers the National Vulnerability Database (NVD), GitHub Security Advisories, and OSV.dev.
How many CVEs does ruby-lsp have?
ruby-lsp has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is ruby-lsp safe to use after a breach?
With no reported breaches, ruby-lsp appears safe based on available data.
Where can I check ruby-lsp's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for ruby-lsp. View the full trust analysis at nerq.ai/safe/ruby-lsp.

Updated June 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy