@tscircuit/runframe@0.0.3137
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe main flagged credential flow is ordinary user-initiated sign-in to the tscircuit registry. However, the browser bundle also enables runtime analytics by default and sends the embedding hostname with activity data, which is identifying telemetry without a disclosed consent mechanism.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Importing the shared browser bundle initializes PostHog; rendering CircuitJsonPreview captures activity.
Impact
The package operator's analytics service can learn the hostname where the component is embedded and associate it with usage activity.
Mechanism
PostHog telemetry is enabled unless disabled through a global flag or the page is on localhost. The telemetry identity can include the embedding domain, and activity events include component, embed status, and active tab.
AI rationale
The main flagged credential flow is ordinary user-initiated sign-in to the tscircuit registry. However, the browser bundle also enables runtime analytics by default and sends the embedding hostname with activity data, which is identifying telemetry without a disclosed consent mechanism.
Evidence
dist/chunk-FHK37NYO.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 bundle initializes PostHog telemetry by default, with an opt-out global flag.
- Telemetry derives an embed domain from the document referrer or current hostname and includes it with an anonymous ID in captured events.
- Rendering CircuitJsonPreview automatically captures activity fields including component, embed status, and active tab.
- The telemetry endpoint is https://postpig.tscircuit.com.
Evidence against
- Telemetry is disabled on localhost by default and can be disabled with TSCIRCUIT_TELEMETRY_DISABLED.
- The inspected sign-in flow sends its login-page token to the tscircuit registry service for the user's requested login.
- The manifest has no install, preinstall, or postinstall scripts.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependency
Source & flagged code
4 flaggeddist/chunk-FHK37NYO.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-FHK37NYO.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-FHK37NYO.jsView on unpkg3810if (!easyedaBrowserPromise) {
L3811: easyedaBrowserPromise = import(
L3812: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-FHK37NYO.jsView on unpkg · L3810Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-FHK37NYO.js
MediumDynamic Requiredist/chunk-FHK37NYO.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumAi Review Evidencedist/chunk-FHK37NYO.js
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3137.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3137 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.