registry / @tscircuit/runframe / 0.0.3087
@tscircuit/runframe@0.0.3087
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection did not substantiate the scanner's exfiltration claim: the credential-bearing requests are part of a user-started registry login flow. The observed telemetry reports runtime errors to a tscircuit host and has a disable setting, so the package is clean.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Analytics runs when the browser bundle initializes and encounters runtime errors; registry authentication begins when a user selects Sign In.
Impact
The inspected behavior supports product diagnostics and registry authentication; it does not establish covert credential theft or an unrelated data transfer.
Mechanism
Error messages and stacks are sent to the tscircuit telemetry host unless telemetry is disabled. The login flow sends its temporary login-page token to registry login endpoints.
AI rationale
Source inspection did not substantiate the scanner's exfiltration claim: the credential-bearing requests are part of a user-started registry login flow. The observed telemetry reports runtime errors to a tscircuit host and has a disable setting, so the package is clean.
Evidence
dist/chunk-L5SCMAHY.jsdist/runner.js
Network endpoints2
postpig.tscircuit.comregistry-api.tscircuit.com
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points consumers to the browser-facing preview and runner bundles and contains no install lifecycle hook.
- The runner starts its login flow from a Sign In button and requests a login page through the registry client.
- The login-page token is sent to registry login-page endpoints; the client defaults to the tscircuit registry API and allows an explicit API base override.
- The telemetry code runs in browsers, honors a disable setting, skips localhost by default, and reports error messages and stacks to the tscircuit telemetry host.
- The inspected dependency manifests and entry files identify the expected core, evaluation-worker, and debug libraries; no attack behavior was established in those inspected paths.
- The flagged bundle is the package's exported UI bundle; its inspected runtime behavior did not establish credential harvesting or transfer of full application records.
Evidence against
- The scanner's exfiltration label is not supported by the inspected login flow: its credential-bearing requests exchange a login-page token with the configured registry API.
- Telemetry does send runtime error details by default unless disabled, but the inspected code identifies the tscircuit telemetry host and limits these events to errors rather than demonstrating covert collection of full application records.
Source & flagged code
4 flaggeddist/chunk-L5SCMAHY.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-L5SCMAHY.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-L5SCMAHY.jsView on unpkg3722if (!easyedaBrowserPromise) {
L3723: easyedaBrowserPromise = import(
L3724: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-L5SCMAHY.jsView on unpkg · L3722Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-L5SCMAHY.js
MediumDynamic Requiredist/chunk-L5SCMAHY.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.3087.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3087 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.