Was slack-ruby-client Hacked?

No Publicly Reported Incidents. As of May 2026, slack-ruby-client 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 slack-ruby-client's security posture as strong (security dimension score: 90/100). Trust Score: 68/100 (B-). Last checked: 2026-04-30.

No Publicly Reported Incidents

Security Incident Summary

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

What We Check

Full Trust Analysis

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

FAQ

Has slack-ruby-client been hacked?
As of May 2026, slack-ruby-client 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 slack-ruby-client have?
slack-ruby-client has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is slack-ruby-client safe to use after a breach?
With no reported breaches, slack-ruby-client appears safe based on available data.
Where can I check slack-ruby-client's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for slack-ruby-client. View the full trust analysis at nerq.ai/safe/slack-ruby-client.

Updated May 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy