registry / @tscircuit/runframe / 0.0.3052
@tscircuit/runframe@0.0.3052
⚠ Under review[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected analytics behavior uses a tscircuit-hosted endpoint and exposes no confirmed attack surface. The package declares and imports @tscircuit/core and @tscircuit/eval, but their source was unavailable in this inspection, so the package cannot be marked clean.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
The analytics code initializes when the bundle loads in a browser; RunFrame activity is recorded when the component renders.
Impact
The inspected transfer is consistent with package analytics, but the unresolved runtime dependencies prevent a complete assessment of package behavior.
Mechanism
The analytics code sends activity properties and an embedding domain or anonymous identifier to its configured tscircuit-hosted service.
AI rationale
The inspected analytics behavior uses a tscircuit-hosted endpoint and exposes no confirmed attack surface. The package declares and imports @tscircuit/core and @tscircuit/eval, but their source was unavailable in this inspection, so the package cannot be marked clean.
Evidence
package.jsondist/runner.jsdist/chunk-3ASA5D4L.js
Network endpoints1
postpig.tscircuit.com
Decision evidence
public snapshotAI called this Manual Review at 72.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest declares @tscircuit/core and @tscircuit/eval as runtime dependencies, and the runner imports both.
- The runner records RunFrame activity when its component renders, including the active tab and embedding status.
- The bundle initializes analytics for browser use and sends activity data with an embedding domain or anonymous identifier to a tscircuit-hosted endpoint.
- The available source does not resolve the behavior of the core and eval runtime dependencies.
Evidence against
- The inspected analytics payload contains activity and identity fields; no credential transfer or unrelated recipient was identified in those excerpts.
- The telemetry can be disabled through a browser setting, and localhost tracking is gated.
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependency
Source & flagged code
4 flaggeddist/chunk-3ASA5D4L.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-3ASA5D4L.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-3ASA5D4L.jsView on unpkg3725if (!easyedaBrowserPromise) {
L3726: easyedaBrowserPromise = import(
L3727: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-3ASA5D4L.jsView on unpkg · L3725Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-3ASA5D4L.js
MediumDynamic Requiredist/chunk-3ASA5D4L.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 Dependency Evidencepackage.json
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3052.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3052 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.