Automatic first-party agent extension setup supports a behavior-specific warning under the supplied policy. No npm lifecycle trigger, foreign agent configuration mutation, or concrete malicious chain was established.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Launching sling unless startup installation is skipped by flags, subcommands, or SKIP_SLING_AUTO_INSTALL.
Impact
Additional third-party agent code is installed and enabled within Sling's environment.
Mechanism
The wrapper reads default package sources and saved settings, then invokes its install command with global scope; the package manager runs npm installation.
Evidence
bin/sling.jssling-default-packages.jsonnode_modules/@earendil-works/pi-coding-agent/dist/core/package-manager.js.sling/agent/settings.json