The manifest has no install hook, and the flagged credential flows use configured Jira credentials for Jira requests or an explicitly called Slack helper. The scheduled PR watcher is opt-in, so the scanner's credential and persistence hints do not establish an attack.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Jira requests and Slack posting occur when their features are called; PR-watch scheduling requires explicit opt-in.
Impact
These paths do not show automatic credential exfiltration or unrequested persistence.
Mechanism
Jira credentials go to the configured Jira base URL, the Slack helper posts to Slack, and the scheduler installs a launch agent or cron entry only when requested.
Evidence
package.jsondist/sandbox.jsdist/jira-rest.jsdist/machine_setup.js
Network endpoints2
slack.comconfigured Jira base URL