Was logrus-runtime-formatter Hacked?

No Publicly Reported Incidents. As of June 2026, logrus-runtime-formatter 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 logrus-runtime-formatter's security posture as strong (security dimension score: 90/100). Trust Score: 48/100 (D). Last checked: 2026-06-15.

No Publicly Reported Incidents

Security Incident Summary

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

What We Check

Full Trust Analysis

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

FAQ

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

Updated June 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy