Was blocking-proxy Hacked?

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

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score70/100 (B)
Security Dimension90/100
Publisherangular
RegistryN/A

What We Check

Full Trust Analysis

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

FAQ

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

Updated July 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy