Was aiohttp-retry Hacked?

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

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score76/100 (B+)
Security Dimension90/100
PublisherDmitry Inyutin
RegistryN/A

What We Check

Full Trust Analysis

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

FAQ

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

Updated June 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy