The package presents itself as a TensorLake SDK, has no install lifecycle hook, and uses TensorLake-specific configuration for its API requests. The network access, credentials, native binding, and CLI launch behavior reviewed are consistent with those functions.
Static reason
No blocking static signals were detected.
Trigger
Network requests occur when SDK operations are called; CLI work occurs when a user invokes a command.
Impact
The observed network and native-loading behavior supports the package’s sandbox, repository, and cloud API functions.
Mechanism
SDK requests use configured TensorLake endpoints and credentials; native code is loaded from the package path selected for the current platform.
Evidence
package.jsondist/index.jslib/runtime.cjsbin/tensorlake-deploy.cjs
Network endpoints2
api.tensorlake.aisandbox.tensorlake.ai