@tscircuit/runframe@0.0.3110
[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 telemetry to its configured analytics host, including identifying embedding-domain data and UI activity, with error details also reportable. This is a warning-level telemetry issue; the flagged registry credentials are used in the explicit sign-in flow.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Importing the browser bundle initializes telemetry; rendering RunFrame records activity, and component errors trigger error reporting.
Impact
The package operator can learn which domains embed the component, how it is used, and details contained in reported errors.
Mechanism
PostHog sends events to https://postpig.tscircuit.com with an embedding hostname or persistent anonymous ID and activity properties.
AI rationale
The package sends undisclosed runtime telemetry to its configured analytics host, including identifying embedding-domain data and UI activity, with error details also reportable. This is a warning-level telemetry issue; the flagged registry credentials are used in the explicit sign-in flow.
Evidence
dist/chunk-5WMHLNFF.jsdist/runner.js
Network endpoints1
postpig.tscircuit.com
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The shared browser chunk initializes PostHog at import time unless telemetry is disabled or the page is localhost.
- Telemetry is sent to https://postpig.tscircuit.com and identifies the embedding domain or a persistent random anonymous ID.
- Mounting RunFrame records its source, component, embed status, and active tab.
- Error telemetry can send error messages and stacks by default.
- Registry credentials are used in the explicit sign-in flow through the registry client.
Evidence against
- The manifest declares no install, preinstall, or postinstall script.
- The sign-in flow is user-triggered and uses the registry client for the tscircuit registry.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-5WMHLNFF.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-5WMHLNFF.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-5WMHLNFF.jsView on unpkg3810if (!easyedaBrowserPromise) {
L3811: easyedaBrowserPromise = import(
L3812: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-5WMHLNFF.jsView on unpkg · L3810Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-5WMHLNFF.js
MediumDynamic Requiredist/chunk-5WMHLNFF.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumAi Review Evidencedist/chunk-5WMHLNFF.js
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3110.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3110 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.