Was git-reword Hacked?

No Publicly Reported Incidents. As of June 2026, git-reword 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 git-reword's security posture as strong (security dimension score: 90/100). Trust Score: 58/100 (C). Last checked: 2026-04-30.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score58/100 (C)
Security Dimension90/100
Publisheryelo
RegistryN/A

What We Check

Full Trust Analysis

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

FAQ

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

Updated June 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy