@tscircuit/runframe@0.0.3073
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe scanner’s hardcoded-exfiltration label is not supported as a confirmed attack: the token transfer follows user sign-in and goes to the run-frame’s configurable file-server API. Because that destination is not validated in the inspected source, warn about conditional credential exposure without blocking publication.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user completes Sign In in the CLI run-frame.
Impact
If the configured API points to an untrusted or unrelated endpoint, it receives the registry token.
Mechanism
The login flow posts the registry token in a TOKEN_UPDATED event to the file-server API, defaulting to /api but allowing a host-page override.
AI rationale
The scanner’s hardcoded-exfiltration label is not supported as a confirmed attack: the token transfer follows user sign-in and goes to the run-frame’s configurable file-server API. Because that destination is not validated in the inspected source, warn about conditional credential exposure without blocking publication.
Evidence
dist/runner.jsdist/chunk-6VJVXFEL.js
Network endpoints2
registry-api.tscircuit.com/api
Decision evidence
public snapshotAI called this Suspicious at 84.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- package.json exposes the browser preview and runner entry points.
- The credential transfer follows the Sign In button and completes a registry login-page exchange.
- The resulting registry token is sent in a TOKEN_UPDATED event.
- That event is posted to a file-server API whose destination can be set by the host page; its default path is /api.
- Separate PostHog telemetry uses the tscircuit-hosted collector and records run-frame identity and activity properties.
Evidence against
- The token transfer follows an explicit sign-in action and supports the CLI run-frame flow.
- The source does not establish that the configurable file-server endpoint is package-controlled or unrelated to the host application.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicense
Source & flagged code
4 flaggeddist/chunk-6VJVXFEL.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-6VJVXFEL.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-6VJVXFEL.jsView on unpkg3725if (!easyedaBrowserPromise) {
L3726: easyedaBrowserPromise = import(
L3727: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-6VJVXFEL.jsView on unpkg · L3725Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-6VJVXFEL.js
MediumDynamic Requiredist/chunk-6VJVXFEL.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.3073.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3073 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.