registry / @tscircuit/runframe / 0.0.3095
@tscircuit/runframe@0.0.3095
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged credential flow is part of an explicit registry login and targets tscircuit’s registry API. The inspected file-server writes are tied to user edits and use the application’s configured server endpoint.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user starts the registry login flow or makes a manual edit in the UI.
Impact
The inspected behavior is consistent with the package’s purpose and does not show unrelated credential collection or exfiltration.
Mechanism
The UI sends login tokens to the tscircuit registry API and sends edit events or file updates to the configured file server.
AI rationale
The flagged credential flow is part of an explicit registry login and targets tscircuit’s registry API. The inspected file-server writes are tied to user edits and use the application’s configured server endpoint.
Network endpoints3
registry-api.tscircuit.com/apiwindow.TSCIRCUIT_FILESERVER_API_BASE_URL
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exports browser UI modules, with no install lifecycle hook shown in its scripts.
- Registry credentials are sent to the tscircuit registry API; the login flow is explicitly initiated through the UI.
- Manual edit events and updated edit files are sent to the configured file server after a user edit.
Evidence against
- The scanner flags credential transport, but the inspected token flow targets the package’s own registry service.
- The package does send edit data over the network, but the inspected handler runs in response to a user edit and uses the file server’s configured base URL.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-7FFNB573.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-7FFNB573.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-7FFNB573.jsView on unpkg3722if (!easyedaBrowserPromise) {
L3723: easyedaBrowserPromise = import(
L3724: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-7FFNB573.jsView on unpkg · L3722Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-7FFNB573.js
MediumDynamic Requiredist/chunk-7FFNB573.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.3095.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3095 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.