The scanner’s credential and execution indicators map to expected app behavior: Playwright browser installation, user-directed test automation, and AI-provider requests. I found no source evidence of browser credential theft, unrelated credential exfiltration, or concealed install-time behavior.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The postinstall hook runs during installation, but its Chromium setup proceeds only for global installs. Runtime behavior starts when the desktop app or CLI is launched and features are used.
Impact
No malicious impact identified in the reviewed source.
Mechanism
The app launches Playwright tests, uses configured AI provider credentials for model requests, and connects to Tesbo when the user supplies an access code. Usage metering is stored locally.
Evidence
scripts/install-chromium.jsbin/atto.jsout/main/index.js
Network endpoints5
api.openai.comopenrouter.aiapi-app-atto.tesbo.ioregistry.npmjs.org