The scanner’s credential and persistence leads map to service-specific operations: Slack posting uses a Slack token with Slack’s API, Jira calls use the configured Jira endpoint, and PR-watch persistence requires an explicit setup call. The manifest has no lifecycle hooks, and the reviewed entry point shows no automatic credential send.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
Slack posting, Jira operations, and PR-watch scheduling are invoked by the application or user; no install hook or automatic import-time trigger was found.
Impact
No evidence of secret collection for an unrelated destination, hidden execution, or automatic persistence.
Mechanism
Slack credentials go to Slack’s API for posting a review request. Jira credentials go to the configured Jira base URL. PR-watch scheduling is an exported setup operation.
Evidence
package.jsondist/sandbox.jsdist/jira-rest.jsdist/machine_setup.js
Network endpoints2
slack.comUser-configured Jira base URL