Was proc_include_dir_as_map Hacked?

No Publicly Reported Incidents. As of June 2026, proc_include_dir_as_map 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 proc_include_dir_as_map'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
PublisherUnknown
RegistryN/A

What We Check

Full Trust Analysis

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

FAQ

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

Updated June 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy