Was SilkCode.REST_API_client Hacked?

No Publicly Reported Incidents. As of July 2026, SilkCode.REST_API_client 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 SilkCode.REST_API_client'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 SilkCode.REST_API_client Trust Score on Nerq.

FAQ

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

Updated July 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy