Composer Scripts

When to use

• The user wants a single script that runs several tools in sequence, such as lint then test then static analysis.
• The user wants to run a task automatically after a Composer install or update, such as clearing a cache or dumping config.
• The user wants a short, named command (like test or lint) that runs a longer tooling invocation.

When NOT to use

• Do not use Composer scripts as the primary orchestrator for a complex, multi-stage build with parallelism and dependencies between targets.
• Do not put application runtime logic in a Composer script; scripts run at the developer or CI command line, never per HTTP request.

Core guidance