registry / @tscircuit/runframe / 0.0.3079
@tscircuit/runframe@0.0.3079
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 8d ago · by lpm-firewall-aiSource inspection resolves the scanner’s credential finding as an interactive registry login and caller-facing token handoff; the configured registry destination defaults to TSCircuit’s registry API. The bundled analytics targets TSCircuit’s telemetry host and records identity and activity properties, with a disable flag; no unrelated credential recipient or concrete attack behavior was established.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user selects Sign In, or the application makes a registry API request using its configured token.
Impact
The reviewed behavior supports intended authentication and product telemetry; it does not establish covert credential collection or transfer to an unrelated recipient.
Mechanism
The runner completes a browser login-page exchange, then emits the new token through TOKEN_UPDATED. Registry API requests use a configured base URL with a TSCircuit registry default; analytics sends identity and activity properties to the TSCircuit PostHog host.
AI rationale
Source inspection resolves the scanner’s credential finding as an interactive registry login and caller-facing token handoff; the configured registry destination defaults to TSCircuit’s registry API. The bundled analytics targets TSCircuit’s telemetry host and records identity and activity properties, with a disable flag; no unrelated credential recipient or concrete attack behavior was established.
Evidence
package.jsondist/runner.jsdist/chunk-AKGYUQVK.js.lpm-dependency-evidence-f956ee86-f9c3-4de4-bc96-0d725824f915/0/npm-linux/package.json.lpm-dependency-evidence-f956ee86-f9c3-4de4-bc96-0d725824f915/0/npm-linux/dist/index.js.lpm-dependency-evidence-f956ee86-f9c3-4de4-bc96-0d725824f915/1/npm-linux/package.json.lpm-dependency-evidence-f956ee86-f9c3-4de4-bc96-0d725824f915/1/npm-linux/dist/worker.js.lpm-dependency-evidence-f956ee86-f9c3-4de4-bc96-0d725824f915/2/npm-linux/package.json.lpm-dependency-evidence-f956ee86-f9c3-4de4-bc96-0d725824f915/2/npm-linux/src/index.js
Network endpoints2
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 exports the preview and runner bundles; reviewed source shows no install-time behavior in the package entrypoint setup.
- The runner exposes sign-in through a visible button. It uses the login-page endpoints and their temporary authorization token to obtain a registry session.
- After successful browser login, the runner sends the new token through its TOKEN_UPDATED event callback.
- Registry requests use the configured registry API URL, defaulting to registry-api.tscircuit.com, and send the registry token as a bearer credential to that service.
- The bundle’s analytics code sends domain or anonymous identity and activity properties to postpig.tscircuit.com; telemetry can be disabled.
- Reviewed dependency excerpts show ordinary package entrypoints, footprint loading from a supplied URL, and worker fetch response handling; they do not establish the flagged credential exfiltration.
Evidence against
- The runner hands the session token to its event callback after login, and the registry API URL can be configured by the consuming application.
- Hosted browser telemetry initializes by default unless disabled, and includes caller-provided activity properties.
Source & flagged code
4 flaggeddist/chunk-AKGYUQVK.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-AKGYUQVK.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-AKGYUQVK.jsView on unpkg3725if (!easyedaBrowserPromise) {
L3726: easyedaBrowserPromise = import(
L3727: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-AKGYUQVK.jsView on unpkg · L3725Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-AKGYUQVK.js
MediumDynamic Requiredist/chunk-AKGYUQVK.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
LowAi Review Evidencepackage.json
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3079.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3079 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.