@tscircuit/runframe@0.0.3078
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe scanner’s exfiltration label overstates the evidence: the login-page token is used with the registry, while the returned session token is forwarded to the CLI event API. Because that destination is configurable and lacks a recipient guard, this is a credential-exposure warning rather than a confirmed attack.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A CLI login is required and the user clicks the sign-in button and completes browser authentication.
Impact
A configured event endpoint can receive the registry token; source inspection does not establish an attacker-controlled recipient or malicious use.
Mechanism
The package exchanges a login-page token with the registry, then posts the returned session token in an event to the configured file-server API.
AI rationale
The scanner’s exfiltration label overstates the evidence: the login-page token is used with the registry, while the returned session token is forwarded to the CLI event API. Because that destination is configurable and lacks a recipient guard, this is a credential-exposure warning rather than a confirmed attack.
Evidence
dist/runner.jsdist/chunk-JVTFIQHY.js
Network endpoints2
registry-api.tscircuit.com${API_BASE}/events/create
Decision evidence
public snapshotAI called this Suspicious at 83.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The manifest points the package’s main export to its browser preview and lists the runner as a separate export.
- The CLI login flow sends its login-page token to the registry API to check login status and exchange it for a session.
- After exchange, the flow places the resulting registry session token in an event that is POSTed to the file-server API.
- The event API defaults to a same-origin path, but the CLI accepts a caller-provided API base URL; the sign-in button activates the flow.
Evidence against
- The login-page token is used for registry login and exchange, and the session token transfer occurs in the CLI login flow after the user clicks Sign In.
- The source does not establish that the configurable file-server endpoint is attacker-controlled or that the token is sent to an unrelated fixed recipient.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
4 flaggeddist/chunk-JVTFIQHY.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-JVTFIQHY.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-JVTFIQHY.jsView on unpkg3725if (!easyedaBrowserPromise) {
L3726: easyedaBrowserPromise = import(
L3727: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-JVTFIQHY.jsView on unpkg · L3725Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-JVTFIQHY.js
MediumDynamic Requiredist/chunk-JVTFIQHY.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumAi Review Evidencepackage.json
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3078.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3078 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.