registry / @tscircuit/runframe / 0.0.3108
@tscircuit/runframe@0.0.3108
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe flagged token belongs to an explicit browser sign-in flow and is exchanged with the package’s registry API. Editor data is sent to the configured file-server API as expected for the package’s editing functions; no unrelated collection or attacker-controlled destination was identified.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Registry requests begin when a user clicks Sign In; file and edit-event requests occur during editor use.
Impact
The inspected flows support user-initiated authentication and editing; no unrelated credential collection or external exfiltration was found.
Mechanism
Login-page credentials go to the configured registry API, defaulting to registry-api.tscircuit.com. Editor file and event requests use the configured file-server API, defaulting to same-origin /api.
AI rationale
The flagged token belongs to an explicit browser sign-in flow and is exchanged with the package’s registry API. Editor data is sent to the configured file-server API as expected for the package’s editing functions; no unrelated collection or attacker-controlled destination was identified.
Network endpoints3
registry-api.tscircuit.com/apiwindow.TSCIRCUIT_FILESERVER_API_BASE_URL
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exports its preview and runner UI modules; the manifest declares no install lifecycle scripts.
- Registry sign-in starts only from a visible Sign In button and opens a browser authentication page.
- The login-page token is used for the registry login-page polling and session-exchange requests; the default registry host is registry-api.tscircuit.com.
- Runframe file and edit-event requests use the configured file-server base URL, which defaults to the same-origin /api path.
Evidence against
- The runner sends edit events and updated manual-edit content to its configured file-server API as part of its editor behavior.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-TA2YJ37G.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-TA2YJ37G.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-TA2YJ37G.jsView on unpkg3810if (!easyedaBrowserPromise) {
L3811: easyedaBrowserPromise = import(
L3812: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-TA2YJ37G.jsView on unpkg · L3810Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-TA2YJ37G.js
MediumDynamic Requiredist/chunk-TA2YJ37G.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.3108.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3108 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.