@tscircuit/runframe@0.0.3111
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe package sends undisclosed runtime analytics that can identify the embedding domain, which fits the suspicious telemetry rule. The credential pointers instead show user-initiated sign-in to the tscircuit registry, with no credential theft identified.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
In a browser, loading the module initializes PostHog; mounting RunFrame or CircuitJsonPreview captures activity.
Impact
The package vendor can associate usage activity with the website embedding the component. The source provides a global opt-out flag, but no user-facing disclosure was found.
Mechanism
The telemetry code identifies users by embedding domain or a persistent random ID and includes the embed domain, component, and active tab in analytics events.
AI rationale
The package sends undisclosed runtime analytics that can identify the embedding domain, which fits the suspicious telemetry rule. The credential pointers instead show user-initiated sign-in to the tscircuit registry, with no credential theft identified.
Evidence
dist/chunk-4AGTJC77.jsdist/runner.js
Network endpoints1
postpig.tscircuit.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- Browser initialization starts PostHog unless a global disable flag is set; telemetry uses https://postpig.tscircuit.com.
- Activity telemetry identifies non-local embedding domains and includes the embed domain and anonymous ID in captured events.
- The component sends activity events when mounted, including the component name and active tab.
- The flagged registry token flow begins only when the user invokes the sign-in handler and uses the configured tscircuit registry.
Evidence against
- The reviewed telemetry contains component activity and domain identity, not credentials, file contents, prompts, or code.
- The credential-related requests are part of an explicit sign-in flow to the package’s own registry service.
- The manifest has no install, preinstall, or postinstall hook.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
4 flaggeddist/chunk-4AGTJC77.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-4AGTJC77.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-4AGTJC77.jsView on unpkg3810if (!easyedaBrowserPromise) {
L3811: easyedaBrowserPromise = import(
L3812: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-4AGTJC77.jsView on unpkg · L3810Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-4AGTJC77.js
MediumDynamic Requiredist/chunk-4AGTJC77.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumAi Review Evidencedist/chunk-4AGTJC77.js
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3111.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3111 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.