License Drift Breaks Open‑Source Chains

When a widely used dependency adopts a nonfree license or changes terms, downstream projects can involuntarily become nonfree or face costly rewrites. Public institutions that run open‑source stacks (schools, NGOs, governments) need active license‑monitoring, contingency plans (alternative implementations), and procurement rules that require license portability or escrow. — This exposes a practical vulnerability in digital public infrastructure: license changes upstream can suddenly force public bodies to choose between running insecure/unmaintained software or undertaking expensive rearchitecture, so policy and procurement must anticipate and mitigate that risk.