How do you detect Trojan Source attacks in JavaScript projects?
Trojan Source hides logic changes in invisible Unicode controls. Scan JavaScript and diffs for bidi characters and mixed-script names in CI.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
Trojan Source hides logic changes in invisible Unicode controls. Scan JavaScript and diffs for bidi characters and mixed-script names in CI.
With custom code you control the fixes and own every bug. With commercial software you control contracts and configuration. Here is what to do for each.
Copyleft licenses such as the GPL, LGPL and AGPL require shared source under set conditions. Learn what triggers the duty and how to check dependencies.
Use multi-stage builds, a small pinned base image, a non-root user, direct node startup and regular rebuilds. Docker and Node.js maintainers agree on this.
Containers package an app with its dependencies and share the host kernel. NIST SP 800-190 groups the risks into images, registries, orchestrators, hosts.
Secure containers by moving checks into the build and the cluster: small base images, non-root runtime, admission rules and one scan gate. Start here.
NIST SP 800-190 groups container risk into images, registries, orchestrators, containers and the host OS. Use the five areas as a checklist.
Harden containers at four layers: images, registries, orchestrators and hosts. NIST SP 800-190 lists the risks and fixes. Start with trusted images
UN Regulation 155 expects carmakers to show supplier risks are managed. See what that means for software parts lists, updates and supplier contracts.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.