@tscircuit/runframe@0.0.3114
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe scanner's credential-exfiltration lead is explained by an interactive TSCircuit registry login flow, with no evidence of credentials sent to an unrelated receiver. However, the browser bundle initializes PostHog automatically and sends usage telemetry with the embedding domain or anonymous ID; under the review rules, undisclosed runtime telemetry warrants a warning.
Decision evidence
public snapshot- The browser bundle initializes PostHog at module load and sends telemetry to https://postpig.tscircuit.com; telemetry can be disabled with a window flag.
- RunFrame activity events include the embedding domain and an anonymous ID, along with component usage properties.
- Registry login is initiated by a Sign In flow that opens a browser authentication page; the returned session token is stored for registry use.
- The package exports browser UI entry points and declares no install lifecycle scripts.
- The credential flow uses the TSCircuit registry login-page exchange and does not show credentials being sent to an unrelated host.
- The telemetry code uses an anonymous identifier or embedding domain rather than showing collection of credentials or file contents.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-BDJB56C7.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-BDJB56C7.jsView on unpkg · L3810Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3114.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3114 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.