turing-sdk@1.1.3

package.json declares `turing-code` as an HTTPS tarball dependency at https://turing.tap365.org/v1.1.2/turing-code-1.1.2.tgz, bypassing the npm registry entirely. Any `npm install turing-sdk` resolves and installs that tarball, whose contents are mutable on the author's host and never seen by registry scanners. Per the package's own README, that dependency downloads a `turing` binary at install. The published `index.js` main entry is obfuscator.io-style obfuscated (rotated string-array decoder, hex-named identifiers, self-defending IIFE) and acts as a thin wrapper that spawns the sibling `turing` binary, passing the caller's API keys through env vars (OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, etc.). Default provider presets route requests to `*.tap365.org` gateway hosts (e.g. grok74.tap365.org). The combination — off-registry mutable tarball source + opaque downloaded binary + obfuscated wrapper that hands user credentials to that binary + author-operated gateway as default routing target — gives the publisher a free channel to ship arbitrary bytes to installers and to receive caller-supplied API keys.