@tscircuit/runframe@0.0.3133
[tscircuit](https://github.com/tscircuit/tscircuit) ⋅ [View Examples](https://runframe.vercel.app)
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe scanner’s credential-flow lead resolves to the package’s registry login flow, which sends its login-page token to the tscircuit registry API. The package has no lifecycle scripts, and the reviewed API requests match RunFrame’s file and event features.
Decision evidence
public snapshot- The package exports browser UI modules; its main entry is dist/preview.js.
- The runner opens a login page as part of its login flow and polls for the result.
- The login flow exchanges a login-page token for a CLI session through the tscircuit registry API.
- File upserts and events are sent to the API as part of the RunFrame application’s file and event features.
- The package manifest declares no lifecycle scripts.
- The login token is used with the tscircuit registry API, whose default host is registry-api.tscircuit.com.
- The reviewed file and event requests send feature data to API_BASE; the excerpts do not show credential discovery or transmission to an unrelated collector.
Source & flagged code
4 flaggedSource sends credentials or rich application records to a package-controlled external receiver enabled by default.
dist/chunk-ZYUOUN2L.jsView on unpkgPackage source references dynamic require/import behavior.
dist/chunk-ZYUOUN2L.jsView on unpkg · L3810Findings
Affected versions and remediation
This report applies to @tscircuit/runframe@0.0.3133.
See all versions of @tscircuit/runframe for other recorded verdicts.
- Review the evidence and your use of @tscircuit/runframe@0.0.3133 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.