The inspected runtime behavior fits a visual-review tool: its CLI supports capture, claim and report flows, while CI publishing uses a workflow credential for the visual-review service. The scanner’s Flutter and IBM host matches are benign strings, and no install-time hook or unrelated credential exfiltration was found.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
CLI commands explicitly selected by the user or CI workflow steps that invoke status publishing; no install lifecycle scripts are declared.
Impact
Expected visual-review reporting and CI status publication; no unrelated credential collection or destination was identified.
Mechanism
The CI status path obtains a workflow OIDC token or configured upload secret and posts it with status data to the visual-review endpoint. The report path uses the GitHub CLI to manage the visual-review PR comment.
Evidence
dist/bin.jsdist/chunk-LC4ZHZOJ.jsdist/chunk-OU25755E.jsdist/chunk-PZC6M3N4.js
Network endpoints2
greedy-jackal-526.convex.sitedocs.flutter.dev