@bakit-org/cli@1.1.9

One or more suspicious static signals were detected.

npm install runs postinstall warning check; user runs ba-kit install/update/uninstall for filesystem changes

User-invoked remote framework content can modify ~/.claude configuration and execute hook scripts during Claude Code events.

GitHub release installer and Claude Code hook registration

The npm package itself does not show hidden theft, persistence, or destructive behavior. Its real risk is that the CLI is an installer for Claude Code assets: explicit install/update commands authenticate with gh, download release archives from bakit-org repositories, merge files into ~/.claude, and register downloaded shell hooks in Claude settings.

Static source inspection supports a warning rather than a block: the lifecycle hook is benign, but the package deliberately installs remote Claude Code hooks and framework files when invoked. This is package-aligned and documented, but it expands an AI-agent control surface with content outside the npm tarball.