Was DevRating.LibGit2SharpClient Hacked?

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

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score46/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 DevRating.LibGit2SharpClient Trust Score on Nerq.

FAQ

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

Updated July 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy