Was Fly CLI (flyctl) Hacked?

No Publicly Reported Incidents. As of April 2026, Fly CLI (flyctl) 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 Fly CLI (flyctl)'s security posture as strong (security dimension score: 90/100). Trust Score: 48/100 (D). Last checked: 2026-04-19.

No Publicly Reported Incidents

Security Incident Summary

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

What We Check

Full Trust Analysis

For a complete safety assessment including privacy, maintenance, and community trust signals, see Fly CLI (flyctl) Trust Score on Nerq.

FAQ

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

Updated April 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy