The scanner’s credential and persistence leads resolve to feature-specific behavior: Slack posting, Jira verification against a configured host, and workspace configuration for a local MCP server. The manifest has no install lifecycle hooks, and machine setup is explicitly invoked.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
No install hook is declared. Machine setup and workspace initialization run through explicit product commands; the inspected credential flows run when their corresponding features are invoked.
Impact
The inspected behavior is consistent with the package’s stated developer-tool functions; no unrelated credential collection or default persistence was established.
Mechanism
Slack review tokens go to Slack’s API for posting a requested review message; Jira credentials go to the configured Jira host for verification; the workspace token configures the local werkmeister MCP endpoint.
Evidence
.devcontainer/devcontainer.json
Network endpoints3
slack.comconfigured Jira base URLhost.docker.internal