@tscircuit/runframe@0.0.3118
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe source shows default runtime telemetry to the publisher’s analytics host that includes identifying domain or persistent-ID data, and the README does not disclose this collection. The reviewed code does not establish credential theft or project-content exfiltration, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- The shared browser chunk initializes PostHog at module load and sends analytics to postpig.tscircuit.com; telemetry can be disabled through a global flag.
- Telemetry identifies users by the embedding domain or a persistent anonymous ID, and includes those identifiers in captured events.
- CircuitJsonPreview automatically reports activity including the active tab and whether it is embedded.
- The telemetry is limited in the inspected activity hook to preview usage fields and identity metadata; no credentials or project files were observed in those events.
- The registry token flow is in a sign-in handler and sends its temporary token to the tscircuit registry API.
- The manifest exports browser UI modules and declares no install or lifecycle scripts.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-R3G6DO22.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-R3G6DO22.jsView on unpkg · L3810Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3118.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3118 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.