registry / @tscircuit/runframe / 0.0.3080
@tscircuit/runframe@0.0.3080
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe flagged credential traffic is a user-triggered registry login exchange, and the configured client targets the registry service. The inspected manifest and required runtime and dependency paths did not establish unrelated collection, an install-time attack, or another concrete attack surface.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user selects the Sign In button.
Impact
No unrelated credential disclosure or other confirmed attack impact was found.
Mechanism
The app opens a registry login page, polls and exchanges a login-page token through registry-specific routes, then stores the returned session token for app use.
AI rationale
The flagged credential traffic is a user-triggered registry login exchange, and the configured client targets the registry service. The inspected manifest and required runtime and dependency paths did not establish unrelated collection, an install-time attack, or another concrete attack surface.
Evidence
package.jsondist/runner.jsdist/chunk-NGPIQUZE.js
Network endpoints1
registry-api.tscircuit.com
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes the preview and runner modules and lists build scripts; it declares no install lifecycle hook.
- The login flow starts from the visible Sign In button and creates a browser login page only when that handler runs.
- The flow polls and exchanges a login-page token through registry login routes, then stores the returned session token for the application.
- The shared registry client defaults to registry-api.tscircuit.com and accepts a registry URL from configuration.
- The inspected dependency entrypoints show circuit component exports, a Comlink worker, and debug runtime selection; no attack behavior was identified in these reviewed paths.
Evidence against
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-NGPIQUZE.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-NGPIQUZE.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-NGPIQUZE.jsView on unpkg3725if (!easyedaBrowserPromise) {
L3726: easyedaBrowserPromise = import(
L3727: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-NGPIQUZE.jsView on unpkg · L3725Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-NGPIQUZE.js
MediumDynamic Requiredist/chunk-NGPIQUZE.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.3080.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3080 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.