registry / @tscircuit/runframe / 0.0.3057
@tscircuit/runframe@0.0.3057
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe scanner’s exfiltration label is not supported by the inspected data flow: the reachable telemetry caller supplies UI activity fields, and the package has no install hook. The package’s browser analytics behavior does not establish a malicious attack surface.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A browser renders RunFrame or CircuitJsonPreview; localhost tracking is disabled unless explicitly enabled.
Impact
The inspected caller sends component, embedding state, and active tab fields; no credential transfer or rich application-record upload was established.
Mechanism
The package initializes PostHog at its configured analytics host and records identity and UI activity fields supplied by the component caller.
AI rationale
The scanner’s exfiltration label is not supported by the inspected data flow: the reachable telemetry caller supplies UI activity fields, and the package has no install hook. The package’s browser analytics behavior does not establish a malicious attack surface.
Evidence
package.jsondist/chunk-4DNJRTDD.jsdist/runner.js
Network endpoints1
postpig.tscircuit.com
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exports browser UI entrypoints and its manifest shows no install lifecycle hook.
- The flagged chunk initializes PostHog in browsers, with telemetry disabled by a window setting and localhost tracking off by default.
- The telemetry helper sends identity fields and caller-provided properties; the RunFrame caller supplies only the component, embedding state, and active tab.
- The inspected dependencies resolve to component exports, a worker module, and a debug utility; their inspected manifests show no install lifecycle hooks.
Evidence against
- The scanner labels the chunk as exfiltrating rich application records, but the inspected telemetry caller provides only UI activity fields.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-4DNJRTDD.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-4DNJRTDD.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-4DNJRTDD.jsView on unpkg3725if (!easyedaBrowserPromise) {
L3726: easyedaBrowserPromise = import(
L3727: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-4DNJRTDD.jsView on unpkg · L3725Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-4DNJRTDD.js
MediumDynamic Requiredist/chunk-4DNJRTDD.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3057.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3057 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.