The risk was already inside the building
Escherbridge
In late March 2024, a small, widely used piece of software for compressing files turned into a security incident. Two recent versions of it, called XZ Utils, had been shipped with malicious code hidden inside. The U.S. Cybersecurity and Infrastructure Security Agency's alert was short: the software might be on a lot of Linux computers, it might let an outsider in, and the advice was to go back to a known-good version and then go looking. Most of the organizations that had it had never chosen it. They had chosen a supplier who had chosen it.
Your suppliers' suppliers are your suppliers
The U.S. standards agency, NIST, publishes a plain checklist for this: know what you build, know what you take in from others, protect the way it gets put together, and be able to say which version each customer is running. A companion guide applies the same list to the automated assembly line most software now runs on, where a poisoned step can look exactly like a successful one. None of it promises to stop a patient attacker. It does make the question "where did this come from, and who approved it?" answerable, which is what a board will ask first.
An add-on is a supplier you let inside
A piece of software that sits unused is one problem. An add-on that your systems run automatically, because a marketplace said it was fine, is the same problem with less warning. The questions are old ones: who vouched for it, what it is allowed to touch, and whether a failed check means it doesn't run or just means someone gets an email. The safe default is no.
The habit, and a better one
The habit is an unaudited plugin supply chain: whatever the registry served, the process runs, and the review happens in the postmortem. The better path is admission before execution. A signature, a sandbox, a role, and a default of no. We hold ourselves to the same sentence. Fractal Engine is alpha, and the plugin host is documented as failing closed — it does not load packages just because they are nearby. The signature field on older log rows is not there yet. That gap gets its own note, with the commits, because a critique that skips our own tree is just a mood. Read it.