The manifest has no install lifecycle hook, and the readable runtime paths fit the package’s TensorLake SDK and CLI purpose. The SDK sends its configured key through the configured TensorLake API flow; no unrelated credential or data collection was identified.
Static reason
No blocking static signals were detected.
Trigger
SDK network requests occur when an application calls SDK operations; packaged CLI binaries run when a user invokes a command.
Impact
No unauthorized credential collection, data exfiltration, or account action was identified in the readable source.
Mechanism
The SDK uses TensorLake-specific configuration and sends its API key in an Authorization header; CLI wrappers pass user arguments and the environment to the selected packaged executable.
Network endpoints2
api.tensorlake.aisandbox.tensorlake.ai