Was serde_derive Hacked?

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

What We Check

Full Trust Analysis

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

FAQ

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

Updated May 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy