Was cli-cursor Hacked?

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

No Publicly Reported Incidents

Security Incident Summary

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

What We Check

Full Trust Analysis

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

FAQ

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

Updated May 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy