Registries Need Built‑In Kill Switches

Package registries distribute code without reliable revocation, so once a malicious artifact is published it proliferates across mirrors, caches, and derivative builds long after takedown. 2025 breaches show that weak auth and missing provenance let attackers reach 'publish' and that registries lack a universal way to invalidate poisoned content. Architectures must add signed provenance and enforceable revocation, not just rely on maintainer hygiene. — If core software infrastructure can’t revoke bad code, governments, platforms, and industry will have to set new standards (signing, provenance, TUF/Sigstore, enforceable revocation) to secure the digital supply chain.