Was docker-compose-logs-processor Hacked?

No Publicly Reported Incidents. As of June 2026, docker-compose-logs-processor 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 docker-compose-logs-processor's security posture as strong (security dimension score: 90/100). Trust Score: 48/100 (D). Last checked: 2026-04-30.

No Publicly Reported Incidents

Security Incident Summary

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

What We Check

Full Trust Analysis

For a complete safety assessment including privacy, maintenance, and community trust signals, see docker-compose-logs-processor Trust Score on Nerq.

FAQ

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

Updated June 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy