@tscircuit/runframe@0.0.3002
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe token transfer is tied to an explicit login action, but the session token is sent to an operator-configurable API endpoint without destination binding. This warrants a warning for conditional credential exposure, not a publish block.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user clicks Sign In and completes CLI login.
Impact
A configured file-server endpoint can receive the tscircuit session token; the source does not establish that the endpoint is hostile or that the token is misused.
Mechanism
The runner exchanges a login-page token for a session, then posts the session token in a TOKEN_UPDATED event to `${API_BASE}/events/create`. The destination can be overridden through apiBaseUrl, with no origin allowlist in the inspected source.
AI rationale
The token transfer is tied to an explicit login action, but the session token is sent to an operator-configurable API endpoint without destination binding. This warrants a warning for conditional credential exposure, not a publish block.
Evidence
dist/runner.jsdist/chunk-NX4JFVSL.js
Network endpoints2
registry-api.tscircuit.com${API_BASE}/events/create
Decision evidence
public snapshotAI called this Suspicious at 94.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest lists build and developer scripts, with no preinstall, install, or postinstall hook.
- The CLI login dialog requires a user click and uses the registry client, whose default host is registry-api.tscircuit.com.
- After the login exchange, the resulting session token is included in a TOKEN_UPDATED event.
- The event sender posts JSON to the file-server API’s /events/create endpoint.
- That API defaults to the same-origin /api path, but the runner accepts an apiBaseUrl override without an origin allowlist.
Evidence against
- The credential transfer follows an explicit sign-in action, and the default event destination is relative to the current origin; source does not establish covert credential theft.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicense
Source & flagged code
4 flaggeddist/chunk-NX4JFVSL.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-NX4JFVSL.js:
const registryApiBaseUrl = getWindowVar("TSCIRCUIT_REGISTRY_API_BASE_URL") || import.meta.env.VITE_TSCIRCUIT_REGISTRY_API_BASE_URL || "https://registry-api.tscircuit.com";
post: (url, options) => getRegistryKy().post(url, options),
var POSTHOG_API_HOST = "https://postpig.tscircuit.com";
return `https://tscircuit.com/editor?${typeParam}#data:application/gzip;base64,${base64Data}`;
const issueUrl = `https://github.com/tscircuit/tscircuit.com/issues/new?title=${encodeURIComponent(
"Initialize a tscircuit project using [tsci init](https://github.com/tscircuit/cli) before adding components.",
"Define reusable modules with cached routes using [<subcircuit />](https://docs.tscircuit.com/elements/subcircuit)",
"Quickly set
Critical
Hardcoded Runtime Data Exfiltration
Source sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-NX4JFVSL.jsView on unpkg3647if (!easyedaBrowserPromise) {
L3648: easyedaBrowserPromise = import(
L3649: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-NX4JFVSL.jsView on unpkg · L3647Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-NX4JFVSL.js
MediumDynamic Requiredist/chunk-NX4JFVSL.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumSuspicious Lifecycle Evidencepackage.json
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3002.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3002 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.