@tscircuit/runframe@0.0.3060
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 13d ago · by lpm-firewall-aiThe exported UI attaches a registry token to requests while allowing the destination to be configured without an allowlist. This supports a conditional credential exposure warning, while the inspected telemetry contains only UI activity fields.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The UI makes a registry request while a registry token is present and a replacement endpoint has been configured.
Impact
The configured recipient can receive the registry credential; the source does not establish that the default tscircuit endpoint is malicious.
Mechanism
The shared API client uses the configured endpoint as its prefix and adds the registry token as a bearer authorization header, without a destination allowlist.
AI rationale
The exported UI attaches a registry token to requests while allowing the destination to be configured without an allowlist. This supports a conditional credential exposure warning, while the inspected telemetry contains only UI activity fields.
Evidence
dist/chunk-H2CJ2PES.js
Network endpoints1
registry-api.tscircuit.com
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package exports a browser UI through dist/preview.js.
- The UI reads a registry token and attaches it as bearer authorization while allowing the registry destination to be replaced through page or build configuration.
- Registry requests use that client in review, order quote, and bug report flows; no destination allowlist appears in the client setup.
- Separate telemetry sends embed and anonymous identifiers plus UI activity fields to a tscircuit-hosted collector.
Evidence against
- The default registry destination is the tscircuit registry, and one separate session-token search sends its token directly to that same service.
- The telemetry activity call supplies UI state rather than project files or registry credentials.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependency
Source & flagged code
4 flaggeddist/chunk-H2CJ2PES.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-H2CJ2PES.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-H2CJ2PES.jsView on unpkg3725if (!easyedaBrowserPromise) {
L3726: easyedaBrowserPromise = import(
L3727: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-H2CJ2PES.jsView on unpkg · L3725Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-H2CJ2PES.js
MediumDynamic Requiredist/chunk-H2CJ2PES.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumAi Review Evidencepackage.json
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3060.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3060 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.