Unpinned npm tools are downloaded and executed, with axe installed globally
Source references: 3The fallback directly uses `npx lighthouse` and runs `npm install @axe-core/cli -g` without pinning versions, requiring preinstalled tooling, or seeking confirmation before installation. `npx` may download and execute code when the package is absent; a global npm install persistently changes the user's tool environment and may run dependency installation scripts. The evidence does not show that these packages are malicious, but this method gives code-execution trust to whatever package versions resolve at that time.
If a package, dependency, or publishing account is compromised at installation time, its code could read or modify files and access credentials available within the agent's permissions. Even without an attack, the global installation may replace or alter an existing CLI version and affect later projects.
The candidate matches the active fallback workflow: it supplies an unpinned `npx lighthouse` execution command and a global axe CLI installation command. The former may download before execution when absent, while the latter persistently changes the global npm environment; both make executed content depend on supply-chain versions resolved at runtime. The evidence does not show the packages are malicious, but users can restrict network installs, global writes, and install scripts and require pinned, reviewed versions.
# Lighthouse accessibility auditnpx lighthouse https://example.com --only-categories=accessibilityShow 2 other places
# axe-corenpm install @axe-core/cli -gaxe https://example.com```If the live tools are unavailable, use Lighthouse CLI or axe for automated coverage and complete the same manual checks. Automated tools detect only a subset of accessibility barriers: a score of 100 is not WCAG conformance, and a low score does not replace issue-level evidence.