@tscircuit/runframe@0.0.3103
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package sends runtime analytics containing the embedding domain and preview activity without documenting the collection in its README. The separate registry-token flow is behind an explicit sign-in action and uses the file-server API, so I found no basis to classify the token flow as exfiltration.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Automatically when CircuitJsonPreview renders in a browser, unless telemetry is disabled through a global flag.
Impact
The package operator can associate preview activity with the embedding site; source reviewed does not show circuit contents or credentials in this telemetry.
Mechanism
PostHog captures an anonymous identifier, embedding domain, and component activity properties and sends them to https://postpig.tscircuit.com.
AI rationale
The package sends runtime analytics containing the embedding domain and preview activity without documenting the collection in its README. The separate registry-token flow is behind an explicit sign-in action and uses the file-server API, so I found no basis to classify the token flow as exfiltration.
Evidence
dist/chunk-HHG77KHT.js
Network endpoints3
postpig.tscircuit.comregistry-api.tscircuit.comsame-origin /api by default
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The browser bundle initializes PostHog with the package’s analytics host; telemetry can be disabled with a global flag.
- Captured telemetry includes the embedding domain, anonymous ID, and component activity properties.
- Rendering CircuitJsonPreview automatically invokes the activity capture hook.
- The registry token flow is behind a Sign In button and sends the token to the file-server event API, which defaults to same-origin /api.
Evidence against
- The telemetry payload shown contains app context and an anonymous identifier, not circuit contents or credentials.
- The package provides a telemetry-disable flag.
- The registry token is sent only after the user completes the sign-in flow. No install lifecycle scripts are declared.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependency
Source & flagged code
4 flaggeddist/chunk-HHG77KHT.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-HHG77KHT.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-HHG77KHT.jsView on unpkg3810if (!easyedaBrowserPromise) {
L3811: easyedaBrowserPromise = import(
L3812: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-HHG77KHT.jsView on unpkg · L3810Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-HHG77KHT.js
MediumDynamic Requiredist/chunk-HHG77KHT.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumAi Review Evidencedist/chunk-HHG77KHT.js
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3103.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3103 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.