@tscircuit/runframe@0.0.3115
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe source sends identifying runtime telemetry by default: it reports the embedding domain and preview activity to the package's analytics host. The flagged registry bearer token is part of an interactive sign-in flow to the configured tscircuit registry, so the evidence supports a telemetry warning rather than malicious credential theft.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Browser import initializes analytics, and rendering CircuitJsonPreview reports activity.
Impact
The vendor can associate activity with the domain embedding the preview, which is identifying runtime telemetry.
Mechanism
PostHog events include the embedding domain, anonymous ID, component, and active tab. A global flag can disable telemetry, but the behavior is not disclosed in the inspected package source.
AI rationale
The source sends identifying runtime telemetry by default: it reports the embedding domain and preview activity to the package's analytics host. The flagged registry bearer token is part of an interactive sign-in flow to the configured tscircuit registry, so the evidence supports a telemetry warning rather than malicious credential theft.
Evidence
dist/chunk-KYDBJBL6.js
Network endpoints1
postpig.tscircuit.com
Decision evidence
public snapshotAI called this Suspicious at 88.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- Browser telemetry initializes by default; source includes a global opt-out flag.
- Telemetry sends the embedding domain and a persistent anonymous ID to the package's PostHog host.
- Rendering CircuitJsonPreview triggers activity telemetry with the active tab and embedding status.
- The flagged bearer token is used in the interactive sign-in flow with the configurable tscircuit registry endpoint.
Evidence against
- The registry token flow starts in a sign-in handler and uses the registry API base URL, rather than sending credentials to an unrelated host.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-KYDBJBL6.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-KYDBJBL6.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-KYDBJBL6.jsView on unpkg3810if (!easyedaBrowserPromise) {
L3811: easyedaBrowserPromise = import(
L3812: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-KYDBJBL6.jsView on unpkg · L3810Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-KYDBJBL6.js
MediumDynamic Requiredist/chunk-KYDBJBL6.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumAi Review Evidencedist/chunk-KYDBJBL6.js
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3115.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3115 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.