Software supply chain attack timeline, 2018 to 2026
A sourced reference timeline of ten supply chain incidents from event-stream in 2018 to the 2026 npm worm, with dates, mechanism and the lesson of each.
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.
A sourced reference timeline of ten supply chain incidents from event-stream in 2018 to the 2026 npm worm, with dates, mechanism and the lesson of each.
In a fab, software runs equipment that acts on physical processes. SEMI E187 and E188, NIST and ISA guidance show where supply chain controls apply.
In a fab, start with the tools. SEMI E187 sets a cybersecurity baseline for fab equipment. Here is what it covers, what it skips and how to use it.
Fab tools mix PCs, controllers and firmware. Ask for software and hardware BOMs, track versions per tool, and use OT guidance for segmentation.
An agent that can act on tools changes who holds authority in a fab. See what standards say, which questions to ask, and where the evidence stops.
Open weights are free to download, but running them is not. See which costs fall on you, with published Hugging Face hardware prices fetched 18 Oct 2026.
Using published prices fetched on 18 October 2026, compare seats, API tokens and a rented GPU for five security analysts, and see which numbers drive each.
A one page release checklist for engineers: code, dependencies, secrets, build provenance, verification and rollback, each tied to a public standard.
A 20 item release security checklist covering code, dependencies, secrets, build integrity and rollback, informed by NIST SSDF, SLSA and OWASP ASVS.
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.