Was exec_stream Hacked?

No Publicly Reported Incidents. As of July 2026, exec_stream 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 exec_stream's security posture as strong (security dimension score: 90/100). Trust Score: 48/100 (D). Last checked: 2026-06-15.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score48/100 (D)
Security Dimension90/100
Publishersidorares
RegistryN/A

What We Check

Full Trust Analysis

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

FAQ

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

Updated July 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy