@tscircuit/runframe@0.0.3107
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe bundle sends the embedding hostname and RunFrame activity metadata to its PostHog host by default, with only a global opt-out visible in the source. This is suspicious runtime telemetry; the flagged registry token flow is part of explicit sign-in to the package’s own service.
Decision evidence
public snapshot- The browser bundle initializes PostHog telemetry by default, with a global opt-out flag.
- Telemetry identifies non-local embeds using the referring or current hostname and sends that domain with activity events.
- The activity hook sends component, embed status, active tab, and source metadata when those properties change.
- The registry token flow is tied to a sign-in handler and sends its login token to the tscircuit registry.
- The telemetry uses the package’s PostHog host and includes an opt-out setting; no credential exfiltration was identified.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-MLY5J6XM.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-MLY5J6XM.jsView on unpkg · L3810Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3107.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3107 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.