@tscircuit/runframe@0.0.3044
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe source confirms a token transfer but does not establish that the default same-origin event endpoint is an unrelated or publisher-controlled recipient, so blocking is not supported. The unbound configurable API base leaves a real credential exposure risk and warrants a warning.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user completes CLI login.
Impact
A server at a configured API base may receive a reusable registry session token; the inspected source does not establish that the default recipient is unrelated or publisher-controlled.
Mechanism
The login handler places the session token in a TOKEN_UPDATED event, which the event sender posts to API_BASE/events/create without a visible recipient allowlist.
AI rationale
The source confirms a token transfer but does not establish that the default same-origin event endpoint is an unrelated or publisher-controlled recipient, so blocking is not supported. The unbound configurable API base leaves a real credential exposure risk and warrants a warning.
Evidence
dist/runner.jsdist/chunk-L4U6MCRO.js
Network endpoints2
/api/events/createregistry-api.tscircuit.com
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The CLI login obtains a registry session token and stores it in the browser runtime.
- After login, the package posts that token in a TOKEN_UPDATED event.
- The event sender posts event data to API_BASE/events/create.
- API_BASE uses a preconfigured global value when present and otherwise defaults to the relative /api path.
- A separate package-search call sends a supplied session token to the tscircuit registry endpoint.
Evidence against
- The token transfer follows an explicit user-initiated CLI login.
- The event endpoint defaults to the same-origin /api path, and the source does not establish a publisher-controlled recipient.
- The separate package-search caller sends its token to the registry service.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicense
Source & flagged code
4 flaggeddist/chunk-L4U6MCRO.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-L4U6MCRO.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-L4U6MCRO.jsView on unpkg3725if (!easyedaBrowserPromise) {
L3726: easyedaBrowserPromise = import(
L3727: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-L4U6MCRO.jsView on unpkg · L3725Findings
1 Critical7 Medium4 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-L4U6MCRO.js
MediumDynamic Requiredist/chunk-L4U6MCRO.js
MediumNetwork
MediumOversized Source Filedist/standalone.min.js
MediumStructural Risk Force Deep Review
MediumGit Dependency
MediumWildcard Dependency
MediumAi Review Evidencedist/runner.js
LowScripts Present
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3044.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3044 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.