@tscircuit/runframe@0.0.3106
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe static scanner’s credential-exfiltration alert is not supported: the registry token flow is for an explicit sign-in to the package’s own registry. However, the bundle enables runtime analytics by default and reports the embedding domain, which is identifying host information, so this is suspicious telemetry.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Importing the browser bundle initializes PostHog; rendering CircuitJsonPreview triggers activity events.
Impact
The package operator can associate RunFrame activity with the host site where it is embedded.
Mechanism
The bundle derives an embed domain from the referrer or page hostname and includes it with activity properties in PostHog events. A global window flag can disable telemetry.
AI rationale
The static scanner’s credential-exfiltration alert is not supported: the registry token flow is for an explicit sign-in to the package’s own registry. However, the bundle enables runtime analytics by default and reports the embedding domain, which is identifying host information, so this is suspicious telemetry.
Evidence
dist/chunk-E3PSHAGJ.js
Network endpoints2
postpig.tscircuit.comregistry-api.tscircuit.com
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The bundled code initializes PostHog at import time unless a global opt-out is set; tracking is enabled by default.
- Telemetry identifies the embedding site using its domain and sends that domain along with activity properties such as component and active tab.
- Rendering CircuitJsonPreview triggers activity telemetry, so it can report usage without a separate telemetry prompt.
Evidence against
- The manifest declares no install, preinstall, or postinstall hook.
- The flagged registry token flow is part of an explicit sign-in handler and targets the tscircuit registry service.
- No evidence shows credentials or project files being sent to an unrelated collector.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-E3PSHAGJ.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-E3PSHAGJ.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-E3PSHAGJ.jsView on unpkg3810if (!easyedaBrowserPromise) {
L3811: easyedaBrowserPromise = import(
L3812: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-E3PSHAGJ.jsView on unpkg · L3810Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-E3PSHAGJ.js
MediumDynamic Requiredist/chunk-E3PSHAGJ.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumAi Review Evidencedist/chunk-E3PSHAGJ.js
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3106.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3106 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.