Was unicode-property-aliases-ecmascript Hacked?

No Publicly Reported Incidents. As of May 2026, unicode-property-aliases-ecmascript 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 unicode-property-aliases-ecmascript's security posture as strong (security dimension score: 90/100). Trust Score: 63/100 (C+). Last checked: 2026-04-30.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score63/100 (C+)
Security Dimension90/100
Publishergoogle-wombot
RegistryN/A

What We Check

Full Trust Analysis

For a complete safety assessment including privacy, maintenance, and community trust signals, see unicode-property-aliases-ecmascript Trust Score on Nerq.

FAQ

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

Updated May 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy