eds-project-health

To audit an AEM Edge Delivery Services project for upgrade risks, run a health check that validates core files like scripts/aem.js, detects boilerplate drift, scores findings A–F, and outputs a prioritized remediation plan.

CSS selector leakage in EDS block structures occurs when styles escape their expected scope, which happens when blocks/* files deviate from standard JS/CSS pairing and decoration patterns during project development or boilerplate updates.

You can check EDS boilerplate integrity by comparing core files such as scripts/aem.js and scripts/aem.css against expected upstream behavior to detect drift and flag core modification risks before they block upgrades.

Eager Lazy Delayed performance anti-patterns in EDS projects include improper resource loading sequences, render-blocking assets, and project-level pitfalls that regress expected performance patterns during go-live preparation or post-boilerplate updates.

Yes, the EDS project audit validates critical configuration files including fstab.yaml and checks related configuration such as helix-query.yaml when present to ensure overall project configuration health.

You should run a project health audit on your aem.live codebase during onboarding, go-live preparation, post-boilerplate updates, and for periodic hygiene checks to identify performance regressions and configuration issues across the repo structure.