Security updates
Most of your site is code you did not write.
A custom site depends on hundreds of open-source libraries. OWASP’s current Top 10 puts failures in that supply chain third on its list of web security risks, and names not upgrading frameworks and dependencies in time as one of the causes. The UK’s data regulator notes that attackers commonly exploit known vulnerabilities for which a patch already existed.
So updates are watched, not remembered. Tools such as npm’s audit and GitHub’s Dependabot report an affected library, the fix is applied, and the integrity check runs before the change reaches visitors. The UK’s cyber security centre advises installing updates promptly, ideally within a few days.
- Framework and runtime on supported versions
- Known vulnerabilities in dependencies fixed
- Every update tested before it goes live



