@getstackrun/sdk@1.1.0
Official JavaScript/TypeScript SDK for STACK - the runtime control plane for AI agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe interactive OAuth setup sends the host's hostname to the SDK API as client registration metadata before browser approval. This is a limited identifying disclosure, so the package is suspicious rather than malicious.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
An unauthenticated API request when the process has a TTY, is not in CI, and STACK_AUTH_INTERACTIVE is not false.
Impact
The API receives a machine-identifying hostname during sign-in setup.
Mechanism
The SDK reads os.hostname(), places it in the OAuth client_name, and registers the client with its configured API base URL before opening the browser for approval.
AI rationale
The interactive OAuth setup sends the host's hostname to the SDK API as client registration metadata before browser approval. This is a limited identifying disclosure, so the package is suspicious rather than malicious.
Evidence
dist/browser-bootstrap.jsdist/client.js
Network endpoints2
api.getstack.run/oauth/registerconfigured STACK_API_URL/oauth/register
Decision evidence
public snapshotAI called this Suspicious at 78.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Interactive OAuth registration sends a client_name containing the machine hostname to the API.
- The hostname is read and included in the registration name before the browser approval flow.
Evidence against
- The browser sign-in path is gated on a TTY and can be disabled with STACK_AUTH_INTERACTIVE=false; CI also disables it.
- The flow is for obtaining credentials for the SDK's own API, and the client name is intended to help identify the client in the dashboard.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
5 flaggeddist/browser-bootstrap.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @getstackrun/sdk@0.17.0
matchedIdentity = npm:QGdldHN0YWNrcnVuL3Nkaw:0.17.0
similarity = 0.361
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/browser-bootstrap.jsView on unpkg181async function openBrowser(url) {
L182: const { spawn } = await import('node:child_process');
L183: try {
High
Child Process
Package source references child process execution.
dist/browser-bootstrap.jsView on unpkg · L181dist/agent-auth.js#virtual:normalized:round1View file
73* Spawn a one-shot loopback HTTP server on a random free port, open
L74: * the dashboard /sdk-bootstrap page in the user"s browser, and resolve\n * with the enrollment ticket once the user approves (or reject on\n * deny / timeout). Used as the interact...
L75: * (or sk_live_* via STACK_API_KEY). No browser, no human-in-the-
Findings
1 Critical4 High2 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/browser-bootstrap.js
HighChild Processdist/browser-bootstrap.js
HighCommand Output Exfiltrationdist/agent-auth.js#virtual:normalized:round1
HighTrigger Reachable Command Output Exfiltrationdist/agent-auth.js#virtual:normalized:round1
HighSemantic Analysis Limiteddist/agent-auth.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @getstackrun/sdk@1.1.0.
See all versions of @getstackrun/sdk for other recorded verdicts.
- Review the evidence and your use of @getstackrun/sdk@1.1.0 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.