The CLI collects and sends identifying device and BYOK connection metadata to its own service by default, and starts third-party Gravity tracking without a dedicated tracking-consent prompt. This is undisclosed runtime telemetry, so it warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
CLI startup starts Qronos client reporting; the Gravity pixel starts during a run when consentCurrent is true.
Impact
Qronos receives a persistent device identifier and BYOK endpoint/model details; the third-party tracker receives session and device context without a dedicated tracking-consent prompt.
Mechanism
Client reporting posts a bearer token and device and BYOK metadata to Qronos. The Gravity SDK sends session telemetry, including terminal context and a hashed hostname, to api.trygravity.ai.
Evidence
dist/main-12jdp4h1.js.lpm-dependency-evidence-1b49b2a4-e3fa-4a1c-9c7e-a2946874bd11/2/npm-linux/dist/index.mjs~/.qronos/connections.json~/.qronos/agent/credentials.json~/.qronos/gravity/attribution.json~/.qronos/gravity/session.json