registry / @tscircuit/runframe / 0.0.3003
@tscircuit/runframe@0.0.3003
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe flagged runtime code uses tscircuit-aligned analytics and registry endpoints, and the inspected token transfer targets the tscircuit registry. The manifest exposes browser modules and contains no install lifecycle hook in the inspected scripts.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Analytics starts when the browser module loads; activity and error events are emitted from runtime hooks, while registry and proxy requests follow their respective UI operations.
Impact
The inspected behavior supports product analytics and service requests; it does not establish credential disclosure to an unrelated recipient or another concrete attack.
Mechanism
Analytics records embedding domain or an anonymous identifier and sends events to the configured tscircuit PostHog host. The package search sends its session token to the tscircuit registry API.
AI rationale
The flagged runtime code uses tscircuit-aligned analytics and registry endpoints, and the inspected token transfer targets the tscircuit registry. The manifest exposes browser modules and contains no install lifecycle hook in the inspected scripts.
Evidence
package.jsondist/chunk-K4QHOAWP.js
Network endpoints2
postpig.tscircuit.comregistry-api.tscircuit.com
Decision evidence
public snapshotAI called this Clean at 88.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes browser UI modules; its scripts list build and development commands, with no install lifecycle hook shown.
- The runtime initializes browser telemetry, with a disable flag and a localhost guard.
- Telemetry uses the tscircuit PostHog host and identifies users by embedding domain or an anonymous ID.
- The package search helper sends its optional session token as a bearer token to the tscircuit registry API.
- The EasyEDA proxy forwards request headers through the configured tscircuit API proxy as part of its proxy function.
Evidence against
Behavioral surface
DynamicRequireNetwork
HighEntropyStringsMinifiedUrlStrings
GitDependencyNoLicenseWildcardDependency
Source & flagged code
4 flaggeddist/chunk-K4QHOAWP.jsView file
•Browser cookie sent to a fixed external endpoint in dist/chunk-K4QHOAWP.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-K4QHOAWP.jsView on unpkg3647if (!easyedaBrowserPromise) {
L3648: easyedaBrowserPromise = import(
L3649: /* @vite-ignore */
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-K4QHOAWP.jsView on unpkg · L3647Findings
1 Critical6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/chunk-K4QHOAWP.js
MediumDynamic Requiredist/chunk-K4QHOAWP.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.3003.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3003 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.