Was SchedulingAgent Hacked?

No Publicly Reported Incidents. As of July 2026, SchedulingAgent 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. Trust Score: 39/100 (E). Last checked: 2026-06-15.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score39/100 (E)
Publisher84de41d99bf475a952b6076acb3f4ac7ea28bda9017e9402
RegistryN/A

What We Check

Full Trust Analysis

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

FAQ

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

Updated July 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy