The package has no npm lifecycle hook, and importing the launcher does not run its command dispatcher. The scanner’s host-configuration and tracker leads correspond to explicit harness setup or user-invoked tracker workflows, while the flagged new test is fixture-based.
Static reason
No blocking static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Host setup occurs when a user explicitly runs `devboard install`; tracker actions are specified by a user-invoked prompt.
Impact
The reviewed behavior does not show unsolicited credential transfer, account actions, or AI-agent configuration changes during package installation or import.
Mechanism
The CLI copies harness integrations into the host, and the tracker prompt uses a wrapper that selects credentials for the host’s repository and invokes the matching forge CLI.
Evidence
AGENTS.md.omp/commands.omp/extensions.omp/mcp.json.devboard/prompts.devboard/extensions.devboard/lib.devboard/scripts/forge-auth.ts