From the thesis to production
The thesis scored known vulnerabilities.
The product extends it to day-zero malware.
Everything below started as a chapter. The one thing the thesis did not attempt, catching a malicious package that has no CVE at the moment of install, is what the same scorer does today at the proxy.
Cross-source database, December 2025 snapshot→840K+ advisories, 250K+ known-malicious package records, 13M+ dependency edges, refreshed continuously
XYZ score, 40 / 30 / 20 / 10 weighting→Six parallel detection signals fused by a cross-signal scorer into allow, alert, quarantine or block
Local CLI agent, xyz scan→xyz Scanner (xyz) on PyPI, the install-time proxy, the VS Code extension and CyberXYZ Gate
Attack-chain detection, ProxyShell and HAFNIUM→Campaign tracking mapped to MITRE ATT&CK, and wave correlation across registries
AI committee: designed in the thesis, never evaluated→Production runs a single model, with code excerpts from the affected release in the prompt, to review alerts