@tscircuit/runframe@0.0.3074
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe scanner’s credential-transfer hint resolves to tokens used in the interactive registry login flow, while the other observed network calls serve editor actions and limited UI telemetry. The inspected source does not establish malicious behavior.
Decision evidence
public snapshot- The manifest exports browser preview and runner modules and defines build scripts without an install lifecycle hook.
- Login tokens are sent through the registry client during the interactive login-page flow; the exchange returns the registry session token.
- Browser telemetry uses the vendor host and sends an anonymous identifier, embedding domain, and UI activity fields; it can be disabled by a global setting.
- Manual edit events are posted to the configured tscircuit API as part of the editor action.
- The inspected dependencies expose circuit components, a worker module, and debug utilities; their inspected entrypoints show no unrelated credential collection or transmission.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-YPWDDM7B.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-YPWDDM7B.jsView on unpkg · L3725Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3074.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3074 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.