The inspected credential flows send values to the corresponding configured services, and the reported persistence requires an explicit user choice. The package has no install lifecycle hook, and the flagged host.docker.internal route is the generated local MCP connection.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Slack posting and Jira API calls occur when their feature functions are invoked; PR watch scheduling requires an explicit setup approval or install command.
Impact
These paths support review notifications, Jira integration, and optional scheduled PR checks; the inspected source does not show unrelated credential collection or automatic persistence.
Mechanism
The package uses configured Slack and Jira credentials with their corresponding services, and uses a workspace token to connect a devcontainer to the local Werkmeister MCP server.
Evidence
package.jsondist/sandbox.jsdist/jira-rest.jsdist/machine_setup.jsdist/devcontainer_gen.js