@tscircuit/runframe@0.0.3134
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe package sends default runtime telemetry to its PostHog host, including the embedding domain and RunFrame activity, without disclosure in the inspected package source. The registry credential flow is user-triggered and goes to the registry service, so the evidence supports a telemetry warning rather than malicious exfiltration.
Decision evidence
public snapshot- The shared browser chunk initializes PostHog automatically unless telemetry is disabled or the page is localhost without an explicit tracking flag.
- PostHog telemetry identifies the embedding domain or a persistent anonymous ID and includes the component's activity properties.
- Rendering RunFrame reports its source, component, embedded status, and active tab.
- The credential flow is tied to a visible Sign In button and uses the tscircuit registry API.
- The telemetry uses a project PostHog key and sends domain or random anonymous identity plus UI activity fields; no unrelated credentials or file contents were found in this flow.
- Registry login exchanges a login-page token with registry-api.tscircuit.com after the user clicks Sign In.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-GFHVKOFE.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-GFHVKOFE.jsView on unpkg · L3810Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3134.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3134 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.