Was njpwerner.autodocstring Hacked?

No Publicly Reported Incidents. As of April 2026, njpwerner.autodocstring 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 njpwerner.autodocstring's security posture as strong (security dimension score: 90/100). Trust Score: 63/100 (C+). Last checked: 2026-04-23.

No Publicly Reported Incidents

Security Incident Summary

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

What We Check

Full Trust Analysis

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

FAQ

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

Updated April 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy