The reviewed behavior is consistent with a TensorLake SDK: configuration and credentials are used for its own API and sandbox services, while the command wrappers run on explicit invocation. The package declares no install lifecycle scripts or unrelated collection behavior.
Static reason
No blocking static signals were detected.
Trigger
API and sandbox network requests occur when SDK operations or listed command-line tools are explicitly used.
Impact
Expected SDK operations against the configured TensorLake services; no unrelated collection or automatic install-time action was found.
Mechanism
The SDK reads TensorLake-specific settings, sends configured credentials as bearer authorization to its API client, and its Python wrapper forwards user-supplied CLI arguments to TensorLake modules.
Network endpoints2
api.tensorlake.aisandbox.tensorlake.ai