Was lock_api Hacked?
No Publicly Reported Incidents. As of June 2026, lock_api 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 lock_api's security posture as strong (security dimension score: 90/100). Trust Score: 63/100 (C+). Last checked: 2026-06-15.
No Publicly Reported Incidents
Security Incident Summary
| CVE Count | 0 |
|---|---|
| Critical CVEs | 0 |
| Breach Status | No Publicly Reported Incidents |
| Trust Score | 63/100 (C+) |
| Security Dimension | 90/100 |
| Publisher | Unknown |
| Registry | N/A |
What We Check
- National Vulnerability Database (NVD) — CVE entries for publicly disclosed vulnerabilities
- GitHub Security Advisories — security alerts for open-source dependencies
- OSV.dev — Google's open-source vulnerability database
- Public breach reports — media reports and incident disclosures
Full Trust Analysis
For a complete safety assessment including privacy, maintenance, and community trust signals, see lock_api Trust Score on Nerq.
FAQ
Has lock_api been hacked?
As of June 2026, lock_api 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 lock_api have?
lock_api has 0 CVE entries (0 critical). CVEs are publicly disclosed vulnerabilities tracked by MITRE and the NVD.
Is lock_api safe to use after a breach?
With no reported breaches, lock_api appears safe based on available data.
Where can I check lock_api's security history?
Nerq monitors NVD (nvd.nist.gov), GitHub Security Advisories, and OSV.dev for lock_api. View the full trust analysis at nerq.ai/safe/lock_api.
Safe? Legit? Scam?
Spyware? Privacy Pros/Cons
Review What is it? Who owns?
Alternatives Use safely
Kids? Trending Leaderboard
Updated June 2026. Trust scores based on automated analysis.