The npm lifecycle hook only configures Git hooks, while the Claude integration runs when the user starts the configured launcher. Its automatic user-level configuration change leaves a broader persistent integration, warranting a warning without evidence of malicious behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Starting a chat through the configured Claude launcher when the chat server file exists.
Impact
Claude sessions using that user configuration gain the package-owned tools and hooks beyond the launched chat.
Mechanism
The launcher registers Parley at user scope and writes Parley pulse hooks into the user's Claude settings file.
Evidence
config/launch/claude-code.shconfig/launch/claude-pulse.mjs$HOME/.claude.json$HOME/.claude/settings.json