Was source-tracking Hacked?

No Publicly Reported Incidents. As of June 2026, source-tracking 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 source-tracking's security posture as strong (security dimension score: 90/100). Trust Score: 87/100 (A). Last checked: 2026-06-15.

No Publicly Reported Incidents

Security Incident Summary

CVE Count0
Critical CVEs0
Breach StatusNo Publicly Reported Incidents
Trust Score87/100 (A)
Security Dimension90/100
Publisherdemianbrecht
RegistryN/A

What We Check

Full Trust Analysis

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

FAQ

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

Updated June 2026. Trust scores based on automated analysis.

We use cookies for analytics and caching. Privacy Policy