@tscircuit/runframe@0.0.3113
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe source performs runtime analytics without an evident disclosure, including the embedding hostname and error messages or stacks, so this is suspicious telemetry. The flagged registry token flow is user-triggered sign-in, and the inspected code does not show it sending discovered credentials to an unrelated host.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Importing the browser entry in a browser, followed by ordinary runtime activity or errors; telemetry can be disabled with TSCIRCUIT_TELEMETRY_DISABLED.
Impact
The package's analytics service can associate usage and error details with the embedding site; this is a privacy risk, but the inspected code does not show credential theft.
Mechanism
The shared chunk initializes PostHog automatically and reports an embed domain, anonymous identifier, and runtime error information.
AI rationale
The source performs runtime analytics without an evident disclosure, including the embedding hostname and error messages or stacks, so this is suspicious telemetry. The flagged registry token flow is user-triggered sign-in, and the inspected code does not show it sending discovered credentials to an unrelated host.
Evidence
dist/preview.jsdist/chunk-RTZ7GSGG.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 browser entry imports the shared chunk, which initializes PostHog at module load when telemetry is not disabled.
- Telemetry identifies the embedding domain from the document referrer or page hostname and sends it with an anonymous ID to https://postpig.tscircuit.com.
- The package also reports runtime error messages, stacks, and circuit JSON errors to PostHog unless telemetry is disabled.
Evidence against
- The registry bearer token flow is part of an explicit Sign In action and exchanges a login-page token for a registry session.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-RTZ7GSGG.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-RTZ7GSGG.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-RTZ7GSGG.jsView on unpkg3810if (!easyedaBrowserPromise) {
L3811: easyedaBrowserPromise = import(
L3812: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-RTZ7GSGG.jsView on unpkg · L3810Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-RTZ7GSGG.js
MediumDynamic Requiredist/chunk-RTZ7GSGG.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumAi Review Evidencedist/preview.js
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3113.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3113 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.